OpenSim.Region.ScriptEngine.DotNetEngine

From OpenSimulator

(Difference between revisions)
Jump to: navigation, search
Line 5: Line 5:
 
DotNetEngine is a ScriptEngine that executes LSL scripts contained within objects.<br />
 
DotNetEngine is a ScriptEngine that executes LSL scripts contained within objects.<br />
 
Developed by Tedd Hansen, development blog: [http://teddmaa.blogspot.com] <br />
 
Developed by Tedd Hansen, development blog: [http://teddmaa.blogspot.com] <br />
<br />
+
 
How it works:<br />
+
----
 +
=How it works=
 
1. Create instance of ScriptEngine(scene).<br />
 
1. Create instance of ScriptEngine(scene).<br />
 
2. ScriptEngine will create instances of:<br />
 
2. ScriptEngine will create instances of:<br />

Revision as of 12:35, 9 August 2007

DotNetEngine

Namespace: OpenSim.Region.ScriptEngine.DotNetEngine

DotNetEngine is a ScriptEngine that executes LSL scripts contained within objects.
Developed by Tedd Hansen, development blog: [1]


How it works

1. Create instance of ScriptEngine(scene).
2. ScriptEngine will create instances of:

EventManager
EventQueueManager
ScriptManager

3. EventManager will hook up all necessary events (all possible script events, script rez, script derez, etc).
4. When events are received, they are processed inside EventManager.

For example:
Event for loading a script will be processed and EventManager will tell ScriptManager to load the script.
Event such as touch_start is received in EventManager and translated to LSL-compatible request before being sent to EventQueueManager.

Note! If event is for a particular object, EventQueueManager will queue event for all scripts inside that object.
5. If script is LSL (LSO ByteCode [2]) then OpenSim.Region.ScriptEngine.DotNetEngine.Compiler.LSL is used to translate the bytecode from LSO to .Net Assembly.
6. On script load, give script a private copy of XXX that it will use to access server. These are commonly know as ll-functions.
6. EventQueueManager has a separate thread running to process its event queue. Events are actually functions inside the script .dll that is called "<state>_event_<event_name>" for example "0_event_touch_start". State is read from a global variable in the script .dll.

Personal tools
General
About This Wiki