Actually if this could be made to be cross platform then it could be turned into a self maintaining external editor as it is the current version is about 8 months out of date as far as the LSL code is concerned. and the way it would end up being self updating is ti could pull directly from the llscript section of the code all the newer LSL functions every time it was built on the LL build farms or even any open source developer currently working on the viewer. Yes i think this would be a nice addition as an optional external editor. to make it cross platform it would have to be converted from .net code to c++ code.
-----Original Message-----
From: Brandon Husbands
Sent: Apr 21, 2011 3:50 PM
To: Mike Chase
Cc: OpenSource Mailing List
Subject: Re: [opensource-dev] Deploying External Editor with Windows build?

The editor does run under mono just fine.
This would be the windows option for the others just select a few.
Maybe have a list of a few that are in the installer as optional.

On Thu, Apr 21, 2011 at 2:33 PM, Mike Chase <mike.ch...@alternatemetaverse.com> wrote:
Unless it can be made available cross platform I don't see a reason to
favor one over another.  Personally I use Eclipse and LSLPlus and the
internal editor for debug tweaks or quick hacks.

Maybe an alongside download or a link on the dev page.  But I wouldn't
think bundling it with the viewer makes sense unless the code is donated
to the project and made to work cross platform. That is, it becomes the
standard LSL editor for everyone.

Mike

On Thu, 2011-04-21 at 15:23 -0400, Oz Linden (Scott Lawrence) wrote:
> On 2011-04-21 14:08, Brandon Husbands wrote:
> > Hey all i own the rights to the source for the LSLEditor.
> > It is publicly GPL but i can license it to ll under any terms they want.
> >
> > Since the external editor feature is ebing added it would be a good
> > idea to deploy that with it.
> > whatcha think?
>
> Your timing is amazing... I'd been meaning to talk to you about that...
>
> I confess to not having tried it yet - what say you, Community ?
>
> Without making any commitments about what will happen - should we make
> it available as an optional component?
> _______________________________________________
> Policies and (un)subscribe information available here:
> http://wiki.secondlife.com/wiki/OpenSource-Dev
> Please read the policies before posting to keep unmoderated posting privileges





--
-------------------------------------------------------------------------------------------------------------------------------
This email is a private and confidential communication. Any use of email may be subject to the laws and regulations of the United States. You may not Repost, Distribute nor reproduce any content of this message.
-------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------
_______________________________________________
Policies and (un)subscribe information available here:
http://wiki.secondlife.com/wiki/OpenSource-Dev
Please read the policies before posting to keep unmoderated posting privileges

Reply via email to