There are criteria why one might be preferred over the other for inclusion in the core code base. Among those: very limited functionality; simplicity with respect to both usability and ease of maintenance and support; and that the code originates from a core contributor. This particular web interfaces satisfies in each respect.<div>
<br></div><div>That said, I suggested that you review the thread again as no one (myself included), is endorsing this code for inclusion as core code.</div><div><br></div><div>Cheers</div><div>James<br><br><div class="gmail_quote">
On Fri, Aug 6, 2010 at 3:07 PM, Melanie <span dir="ltr"><<a href="mailto:melanie@t-data.com">melanie@t-data.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I did. All web front ends are third party developments. I can't see<br>
core preferring one over the others. So none get in.<br>
<font color="#888888"><br>
Melanie<br>
</font><div><div></div><div class="h5"><br>
James Stallings II wrote:<br>
> Thanks for the clarification. Please see the rest of the thread.<br>
><br>
> On Fri, Aug 6, 2010 at 2:43 PM, Melanie <<a href="mailto:melanie@t-data.com">melanie@t-data.com</a>> wrote:<br>
><br>
>> Core does NOT include a web front end. It is always a separate project.<br>
>><br>
>> Melanie<br>
>><br>
>> Ai Austin wrote:<br>
>> > Can I suggest an approach here... as someone who has spent a LOT of<br>
>> > time getting something working for our Openvue and adding in<br>
>> > gradually the functionality as time allows.<br>
>> ><br>
>> > I can say that our grid has a small number of users, and that is<br>
>> > mostly as three attempts to integrate OpensimWI have failed. Though<br>
>> > we use offline IM from that useful offering. We now have Wifi going<br>
>> > as opf yesterday and I just opened up te grid to the Virtual<br>
>> > University of Edinburgh members... whereas for 2 years I could not as<br>
>> > it would need too much manual setup. To me this is a no<br>
>> > brainier. Diva has provided some useful functionality and it is<br>
>> important.<br>
>> ><br>
>> > However, there are alternatives like simian grid, d4os, OpensimWi etc<br>
>> > which provide a lot too.<br>
>> ><br>
>> > Can I suggest an approach...<br>
>> ><br>
>> > Core should be as small as possible. Minimum to get running.<br>
>> ><br>
>> > Other things ought to look like addons. Packed in the addons<br>
>> > directory and separately enableable. By default if in addon they<br>
>> > should be OFF. There can be several alternatives, but at LEAST ONE<br>
>> > for each important function.<br>
>> ><br>
>> > - voice<br>
>> > - web front end<br>
>> > - offline IM<br>
>> > - groups<br>
>> > - ?<br>
>> ><br>
>> > We should be open to anyone adding alternatives. But quality control<br>
>> > means the community ought to use them a while before they get added<br>
>> > into the main download. If they date, no problem, they date, and the<br>
>> > community can decide if and when to remove them from the main<br>
>> > download... they can still be add ons added separately BEFORE compile<br>
>> > or released as binary addons with the same directory structure.<br>
>> ><br>
>> > Refinement and addons to addone (I think this will apply a LOT to<br>
>> > wifi which I can see vast potential for) should be available in a<br>
>> > contributed addons directory.<br>
>> ><br>
>> > Looking good guys... and thanks for all the effort everyone.. and<br>
>> > Diva for this module. Name is odd though :-) 4 users today said they<br>
>> > thought it must relate to something about Wireless Wifi. Wi better?<br>
>> ><br>
>> > See our wifi front end at: <a href="http://virtual.aiaie.d.ac.uk:8002/wifi" target="_blank">http://virtual.aiaie.d.ac.uk:8002/wifi</a><br>
>> ><br>
>> > See which need checking by other Wifi users at<br>
>> > <a href="http://opensimulator.org/wiki/Wifi" target="_blank">http://opensimulator.org/wiki/Wifi</a><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Opensim-dev mailing list<br>
>> > <a 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>
>> ><br>
>> ><br>
>> _______________________________________________<br>
>> Opensim-dev mailing list<br>
>> <a 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>
>><br>
><br>
><br>
><br>
><br>
</div></div>> ------------------------------------------------------------------------<br>
<div><div></div><div class="h5">><br>
> _______________________________________________<br>
> Opensim-dev mailing list<br>
> <a 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>
_______________________________________________<br>
Opensim-dev mailing list<br>
<a 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></blockquote></div><br><br clear="all"><br>-- <br>===================================<br><a href="http://osgrid.org">http://osgrid.org</a><br><a href="http://twitter.com/jstallings2">http://twitter.com/jstallings2</a><br>
<a href="http://www.linkedin.com/pub/5/770/a49">http://www.linkedin.com/pub/5/770/a49</a><br>
</div>