<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>I'm not particular fond of LSL, but in general terms, I do agree with you Mike;<BR>
<BR>
if people are expecting LSL, let's give them that.<BR>
<BR>
If we want to supply something a bit more "OpenSim" lets derive an OSSL Script engine from the LSL Script engine and give the region owner a choice as of what engine should be the 'default' for the region.<BR><BR>
By the way; would it be a bad thing to use the "description" field for a script to set what engine it's supposed to run on?<BR>
<BR>
The description could be something like<BR>
"<LSL> This is my bling bling script"<BR>
or<BR>
"<Python> This is my python script"<BR>
or<BR>
"<C#> This is my c# script"<BR>
<BR>
Where no tag would mean 'default'? (Which in most cases would be the OSSL Engine, that still supports LSL for backwards compatibility?)<BR><BR>Best regards,<BR>Stefan Andersson<BR>Tribal Media AB<BR> <BR>Join the 3d web revolution : <A href="http://tribalnet.se/" target=_blank>http://tribalnet.se/</A><BR> <BR><BR><BR><BR>
<HR id=stopSpelling>
<BR>
> Date: Thu, 11 Sep 2008 11:38:25 +0900<BR>> From: mmazur@gmail.com<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Place for osFoo functions that only work with certain languages<BR>> <BR>> <BR>> Hi,<BR>> <BR>> On Wed, 10 Sep 2008 13:59:59 +0100<BR>> "Rob Smart" <rob.s.smart@gmail.com> wrote:<BR>> <BR>> > I'd like to support the osParseJSON function in LSL as well as C#<BR>> > script making it more available.<BR>> > <BR>> > ...<BR>> > <BR>> > I'd certainly be interested in more dopwerful datatypes being<BR>> > introduced to LSL, the two in particular I'd<BR>> > need to implement would be System.Collections.Hashtable and<BR>> > System.Collections.ListArray.<BR>> <BR>> I don't mean to pick on you specifically, Rob, but I'm not a fan of<BR>> extending LSL in any way.<BR>> <BR>> LSL is Linden Scripting Language, and the authority on this is Linden<BR>> Labs. If we start adding new features to LSL, it ceases to become LSL.<BR>> It becomes LSL++ or something like that.<BR>> <BR>> So, since you require these additional features, why not use one of the<BR>> alternative scripting languages supported by OpenSim? JavaScript<BR>> supports JSON rather well if I'm not mistaken.<BR>> <BR>> I understand that LSL is simple and this is an appealing feature to<BR>> non-programmers. Perhaps an OpenSim specific script language should be<BR>> developed, with these additional features, which can fill this niche?<BR>> <BR>> Mike<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR><BR></body>
</html>