ScriptEngines - Revision history

Ubit: /* OpenSim.ini Settings */

2020-09-22T12:22:51Z

‎OpenSim.ini Settings

2020-09-22T12:21:07Z

‎Script Engines

2020-09-22T12:20:19Z

‎Script Engines

2018-11-16T06:01:43Z

‎Multiple script engine usage

2018-11-16T06:01:02Z

‎Multiple script engine usage

2018-11-16T05:59:33Z

‎Multiple script engine usage

2018-11-16T05:58:52Z

‎Multiple script engine usage

2018-11-16T05:57:46Z

‎Multiple script engine usage

2018-11-16T05:56:42Z

‎Multiple script engine usage

2018-11-16T05:54:59Z

‎Multiple script engine usage

@@ Line 31: / Line 31: @@
 These default to true.
-OpenSimulator is able to run multiple script engines simultaneously.
+OpenSimulator should be able to run multiple script engines simultaneously, but this should be avoid
 == Multiple script engine usage ==

@@ Line 7: / Line 7: @@
 This page deals with common parts of script engines.<br>
-OpenSimulator currently only have two public script engine XEngine and YEngine.br>
+OpenSimulator currently has two public script engines XEngine and YEngine.<br>
- For more information on this, please see [[XEngine]] and [[YEngine]].
+For more information, please see [[XEngine]] and [[YEngine]].
 For information on the old DotNetEngine which was deprecated in OpenSimulator 0.6.8 and subsequently removed from the core tree, please see [[DotNetEngine]] and [[OpenSim.Region.ScriptEngine]].

@@ Line 6: / Line 6: @@
 OpenSimulator supports scripting via script engines.  Script engines are normal region modules.
-This page deals with common parts of script engines, though OpenSimulator currently only have one public script engine (XEngine).  For more information on this, please see [[XEngine]].
+This page deals with common parts of script engines.<br>
 For information on the old DotNetEngine which was deprecated in OpenSimulator 0.6.8 and subsequently removed from the core tree, please see [[DotNetEngine]] and [[OpenSim.Region.ScriptEngine]].

@@ Line 33: / Line 33: @@
 == Multiple script engine usage ==
-To run a script on a specific engine, begin the script with:
+To run a script on a specific engine, begin the script with a first line like:
 <source lang="lsl">
 //XEngine: or //someOtherEngineName:

@@ Line 35: / Line 35: @@
 To run a script on a specific engine, begin the script with:
 <source lang="lsl">
-//XEngine: or //(someOtherEngine):
+//XEngine: or //someOtherEngineName:
 </source>
 Optionally, this can be followed by a language code:
 <source lang="lsl">
 //XEngine:lsl
-//(someOtherEngine):lsl
+//someOtherEngineName:lsl
 </source>
 Beware: there is a little side effect. If you start your script with anything like

@@ Line 89: / Line 89: @@
          internal SceneObjectPart m_host;
          internal uint m_localID;
-         internal LLUUID m_itemID;
+         internal UUID m_itemID;
-         public void Initialize(IScriptEngine ScriptEngine, SceneObjectPart host, uint localID, LLUUID itemID)
+         public void Initialize(IScriptEngine ScriptEngine, SceneObjectPart host, uint localID, UUID itemID)
+         {
              m_ScriptEngine = ScriptEngine;

@@ Line 54: / Line 54: @@
 Compilers take script text and convert it to a .NET assembly. Such an assembly needs to reference a runtime, which provides API stubs.
-This calls out of the appdomain to the API implementation.
+Currently, a compiler exists for lsl.
-−
-Currently, a compiler exists for lsl, c# and vb. YieldProlog (yp) can be added to c# scripts.
 A runtime exists for the LSL API and for the OSSL API. [[LSL Status/Functions]]
 The following describes the directory structure(under /OpenSim/Region/):

@@ Line 76: / Line 76: @@
 |-
 |ScriptEngines/Shared/Api/Runtime/||The Api runtimes (see below)
 |}