<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:arial,helvetica,sans-serif;font-size:12pt"><div>Dear Kr:<br><br>There are hundreds of folks using dotnetengine and it is our default, so I would definitely say it is not deprecated.<br><br>The agreement made with Tedd was that we would endeavour to patch both the LSL_BuiltIn_Commands.cs and the duplicated, morphed, file, LSL_Api.cs until the time occurred when the duplication can be made to go away.<br><br>It is unfortunate that some folks are patching one and not the other, but that is a side affect of the decision we made to duplicate the LSL_BuiltIn_Commands.cs file in the first place. So, we are stuck with this until and unless we can resolve the duplication.<br><br>Charles<br><br><br></div><div style="font-family: arial,helvetica,sans-serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 13px;">-----
Original Message ----<br>From: krtaylor <krtaylor@linux.vnet.ibm.com><br>To: opensim-dev <opensim-dev@lists.berlios.de><br>Sent: Thursday, September 4, 2008 2:30:47 PM<br>Subject: [Opensim-dev] Script engine base functional merge - Dot Net Engine<br><br>
Here's a brief status and some thoughts.<br><br>For those who are new, a recap - I am working to port the DotNetEngine <br>to make use of ScriptEngine.Shared LSL and OSSL, created at the same <br>time as the XEngine, instead of using ScriptEngine.Common. Just as DNE <br>was built around Common, XEngine is built around the use of the new <br>Shared. But, the design for the two engines are very different. The <br>initial refactoring of DNE out of Common removed Remote and moved the <br>classes temporarily into ScriptEngine.DotNetEngine also making use of <br>some of Shared where I could. This is posted in the patch attached to <br>#1780.<br><br>Last week, after a very painful resync to trunk, I started down the path <br>of making ScriptEngine (the name for DNE) implement IScriptEngine. My <br>first attempt was to pull in XScriptInstance. While this was underway, <br>XScriptInstance was moved and refactored out of <a target="_blank"
href="http://XEngine.cs">XEngine.cs</a> into a <br>seperate file <a target="_blank" href="http://ScriptInstance.cs">ScriptInstance.cs</a>. Don't get me wrong, this was a good <br>thing, but once again, I am having to play catch up. The merge target is <br>moving rapidly.<br><br>I went back through commits looking for this refactor and realized that <br>most of the new script engine code, enhancements and fixes are NOT <br>happening to both trees. Most of the patches are for Shared or XEngine <br>only. In my sample period of a few weeks, I only found one patch <br>applied to Common. It appears that the project has made a switch, <br>whether consciously or not. XEngine is becoming the script engine of choice.<br><br>So, I'll throw this out there - Are we still interested in making <br>DotNetEngine an equal partner in our stable of script engines? OR, are <br>we on a road where we are eventually going to deprecate DotNetEngine? <br>Frankly,
from the commit logs from the past several weeks, it appears to <br>be the latter...<br><br>Comments?<br><br>-- <br>Kurt R Taylor (Kurt Stringer)<br><br>Open Virtual Worlds Development<br>International Business Machines, Corp.<br>(512) 838-2496 T/L: 678<br><br><br>_______________________________________________<br>Opensim-dev mailing list<br><a ymailto="mailto:Opensim-dev@lists.berlios.de" href="mailto:Opensim-dev@lists.berlios.de">Opensim-dev@lists.berlios.de</a><br><a href="https://lists.berlios.de/mailman/listinfo/opensim-dev" target="_blank">https://lists.berlios.de/mailman/listinfo/opensim-dev</a><br></div></div></div></body></html>