<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
FONT-SIZE: 10pt;
FONT-FAMILY:Tahoma
}
</style>
</head>
<body class='hmmessage'>+1 Fo' sho'<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>
<HR id=stopSpelling>
> Date: Sat, 7 Jun 2008 12:16:04 -0400<BR>> From: adam@deepthink.com.au<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Should the core OpenSim distribution carrymanyscripting languages?<BR>> <BR>> +1<BR>> <BR>> Adam<BR>> <BR>> -----Original Message-----<BR>> From: opensim-dev-bounces@lists.berlios.de<BR>> [mailto:opensim-dev-bounces@lists.berlios.de] On Behalf Of Justin<BR>> Clark-Casey<BR>> Sent: Saturday, 7 June 2008 12:14 PM<BR>> To: opensim-dev@lists.berlios.de<BR>> Subject: Re: [Opensim-dev] Should the core OpenSim distribution<BR>> carrymanyscripting languages?<BR>> <BR>> Thankyou for all the messages on this topic. It sounds like we have a <BR>> rough consensus that we should try and keep the functionality that ships<BR>> <BR>> with OpenSim down to some set of 'core' modules. I expect that the idea<BR>> <BR>> of what functionality constitutes the core will probably have to be <BR>> decided on a case by case basis, evolving over time.<BR>> <BR>> In this particular case, it sounds like we should not regard Yield <BR>> Prolog as a core module. However, I don't think our modular interface <BR>> (in the area of scripting) is quite advanced enough right now to support<BR>> <BR>> a clean separation (though I haven't looked in any significant detail). <BR>> Therefore, in my opinion this code should remain in the tree and <BR>> receive patches until the necessary underlying work is done to allow <BR>> Yield Prolog to be easily plugged in. I don't think Kinoc follows this <BR>> list but I have made him aware of this discussion and what is likely to <BR>> happen in the future.<BR>> <BR>> As regards non-core module hosting, to me it sounds like the easiest <BR>> first step is to ask module contributors to self host until we build up <BR>> enough modules to justify a repository system. Of course, that doesn't <BR>> stop anyone establishing one in anticipation :) I also like Stefan's <BR>> idea of listing the existing core modules on the wiki, which at least <BR>> would give people some idea of the plugin points that currently exist.<BR>> <BR>> This is an interesting area for me so I hope to be able to do something <BR>> towards making it easy (or easier) to separate out language modules <BR>> soon, assuming no-one else works on this first. I know Sean has also <BR>> expressed his intention to look at mono-addins and the module system in <BR>> general (which also needs to be improved, at the very least to provide <BR>> some general mechanism for including and excluding modules rather than <BR>> relying on the modules to do this for themselves).<BR>> <BR>> Regards,<BR>> <BR>> -- <BR>> justincc<BR>> Justin Clark-Casey<BR>> http://justincc.wordpress.com<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR>> _______________________________________________<BR>> Opensim-dev mailing list<BR>> Opensim-dev@lists.berlios.de<BR>> https://lists.berlios.de/mailman/listinfo/opensim-dev<BR></body>
</html>