OpenSim.Region.ScriptEngine.Common - Revision history

MakoBot: Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

2012-03-04T06:48:40Z

Robot: Replacing 'OpenSim' to 'OpenSimulator', which is the precise name

MakoBot: Robot: Cosmetic changes

2012-03-04T03:43:10Z

Robot: Cosmetic changes

MakoBot: Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

2011-06-10T23:17:00Z

Removed 'Template:' prefix from template includings and/or changed external-link into internal-link

Fritigern at 16:36, 19 November 2010

2010-11-19T16:36:28Z

Fritigern at 13:33, 19 November 2010

2010-11-19T13:33:07Z

Tedd at 18:50, 22 October 2010

2010-10-22T18:50:18Z

Ideia Boa at 23:17, 21 May 2009

2009-05-21T23:17:12Z

Tedd:

2008-01-21T11:40:34Z

<br />

Tedd: Cosmetics

2008-01-21T09:34:10Z

Cosmetics

Tedd: Added AppDomain description

2008-01-20T19:23:49Z

Added AppDomain description

@@ Line 9: / Line 9: @@
 == How to implement your own script engine ==
-Creating a new script engine for OpenSim is simple (haha).<br />
+Creating a new script engine for OpenSimulator is simple (haha).<br />
-What I mean by simple is that if you already have a VM (Virtual Machine) or script engine of some sort then integrating it as a OpenSim ScriptEngine plugin is simple.<br />
+What I mean by simple is that if you already have a VM (Virtual Machine) or script engine of some sort then integrating it as a OpenSimulator ScriptEngine plugin is simple.<br />
 <br />
@@ Line 18: / Line 18: @@
 . What script belongs to what object is automatically taken care of. You just need to provide the scripts classes - nothing else.<br />
 <br />
-. OpenSim events are translated and given to you as LSL events. Your script functions are executed automatically, no need to hook up to events or anything.<br />
+. OpenSimulator events are translated and given to you as LSL events. Your script functions are executed automatically, no need to hook up to events or anything.<br />
 If you want to implement your own event handlers, feel free to do so. Look in "OpenSim.Region.ScriptEngine.Common.ScriptEngineBase.EventManager.cs" how its done. Your own events can run together with LSL events without any problem.<br />
 <br />
@@ Line 31: / Line 31: @@
 === Getting started ===
 . Create a new project named "OpenSim.Region.MySuperScriptEngine" (replace "MySuperScriptEngine" with the name of your scriptengine).<br />
-. Create a new class (file) named "ScriptEngine". It must be named exactly ScriptEngine for OpenSim to use it. ScriptEngine must inherit from "OpenSim.Region.ScriptEngine.Common.ScriptEngineBase.ScriptEngine".<br />
+. Create a new class (file) named "ScriptEngine". It must be named exactly ScriptEngine for OpenSimulator to use it. ScriptEngine must inherit from "OpenSim.Region.ScriptEngine.Common.ScriptEngineBase.ScriptEngine".<br />
 . You need to override a couple of functions. Most probably you don't want to do any special work here, so look below for a sample default file.<br />
 . Create a new class (file) named "ScriptManager" that inherits from "OpenSim.Region.ScriptEngine.Common.ScriptEngineBase.ScriptManager".<br />

@@ Line 6: / Line 6: @@
-=OpenSim.Region.ScriptEngine.Common=
+= OpenSim.Region.ScriptEngine.Common =
-==How to implement your own script engine==
+== How to implement your own script engine ==
 Creating a new script engine for OpenSim is simple (haha).<br />
 What I mean by simple is that if you already have a VM (Virtual Machine) or script engine of some sort then integrating it as a OpenSim ScriptEngine plugin is simple.<br />
 <br />
-===What do I get for free?===
+=== What do I get for free? ===
 . Loading/unloading of scripts are queued and executed in sequence. Only one load/unload at the time.<br />
 <br />
@@ Line 29: / Line 29: @@
 . Long LSL-commands that returns with an event is also handled.<br />
-===Getting started===
+=== Getting started ===
 . Create a new project named "OpenSim.Region.MySuperScriptEngine" (replace "MySuperScriptEngine" with the name of your scriptengine).<br />
 . Create a new class (file) named "ScriptEngine". It must be named exactly ScriptEngine for OpenSim to use it. ScriptEngine must inherit from "OpenSim.Region.ScriptEngine.Common.ScriptEngineBase.ScriptEngine".<br />
@@ Line 36: / Line 36: @@
 . Your ScriptManager class needs to override two functions. One to start a script and one to stop a script.<br />
-===ScriptEngine class===
+=== ScriptEngine class ===
 The main purpose of ScriptEngine class is to be able to intercept scene, for example starting with a "fake" scene instead of OpenSim's scene. You probably don't want this, so just go for the standard initialization.<br />
 A standard class would look like this:<br />
@@ Line 59: / Line 59: @@
+  }
-===ScriptManager class===
+=== ScriptManager class ===
 A script is refecenced by object id "localID" (the object/prim it is inside) and script id "itemID" (the particular (unique) instance of that script). These parameters along with a string "Script" containing the script text (source code) are passed to your (overriden) start script function in your ScriptManager class.<br />
 <br />
@@ Line 102: / Line 102: @@
+  }
-===IScript interface===
+=== IScript interface ===
 So you have implemented the two classes described above. Now how does this connect to your JavaScript or Perl or YourCustomSuperLanguage script engine or VM?<br />
 <br />
@@ Line 116: / Line 116: @@
+  }
-===AppDomain security===
+=== AppDomain security ===
 If you are writing a .Net based script engine and want AppDomain security and loading/unloading then:
   // Load script:
@@ Line 123: / Line 123: @@
    // Unload script:
    m_scriptEngine.m_AppDomainManager.StopScript(LSLBC.Exec.GetAppDomain());
 [[Category:Modules]]

@@ Line 1: / Line 1: @@
 __NOTOC__
-{{Template:Quicklinks}}
+{{Quicklinks}}
 <br />

← Older revision		Revision as of 16:36, 19 November 2010
Line 123:		Line 123:
	// Unload script:		// Unload script:
	m_scriptEngine.m_AppDomainManager.StopScript(LSLBC.Exec.GetAppDomain());		m_scriptEngine.m_AppDomainManager.StopScript(LSLBC.Exec.GetAppDomain());
		+
		+
		+
		+	[[Category:Modules]]

@@ Line 3: / Line 3: @@
 <br />
-=WARNING! THIS PAGE IS OBSOLETE! ScriptEngine has been replaced by xengine!=
+<span style="color:#ff0000;">'''NOTE! THIS PAGE IS OBSOLETE! ScriptEngine has been replaced by XEngine!'''</span>
 =OpenSim.Region.ScriptEngine.Common=

← Older revision		Revision as of 23:17, 21 May 2009
Line 1:		Line 1:
		+	__NOTOC__
		+	{{Template:Quicklinks}}
		+	<br />
		+
	=OpenSim.Region.ScriptEngine.Common=		=OpenSim.Region.ScriptEngine.Common=

← Older revision		Revision as of 19:23, 20 January 2008
Line 112:		Line 112:
	// whatever code for this event... probably calling your own VM's function with the same name? ;)		// whatever code for this event... probably calling your own VM's function with the same name? ;)
	}		}
		+
		+	===AppDomain security===
		+	If you are writing a .Net based script engine and want AppDomain security and loading/unloading then:
		+	// Load script:
		+	IScript CompiledScript = m_scriptEngine.m_AppDomainManager.LoadScript(filename);
		+	and
		+	// Unload script:
		+	m_scriptEngine.m_AppDomainManager.StopScript(LSLBC.Exec.GetAppDomain());