I would be happy if the built-in editor could be upgraded to handle a
larger source code file.
When I code, I am quite heavy on the commenting, as I maintain many
scripts, and I rely on my commenting to refresh my memory about what
I was doing, when I revisit a script that I haven't needed to touch
for quite awhile.
I've had issues with a few of my longer scripts. It seems that when
editing, if the size goes beyond 65535 characters, I will start to
get a beeping sound. If I attempt to save that file, it sometimes
fails to compile because I have lost parts of it off the end of the
file...parts which sometimes I have to re-create from memory. I
usually have to start removing comments, or commented-out code, just
to be able to save the file.
A basic function like this, shouldn't be asking for too much.
Otherwise, I wish I had a way to copy my source scripts to my
computer without having to constantly resort to using copy/paste all the time.
Andro
At 01:28 PM 3/4/2010, you wrote:
On Wed, Mar 3, 2010 at 7:03 AM, Jonathan Irvin
<<mailto:djfoxys...@gmail.com>djfoxys...@gmail.com> wrote:
I do often hear complaints and wishes for new build tools, what
about us LSL devs? Some things I would like are:
Better IDE in SL Viewer
API for compiling in LSL using various IDEs already available
Going along with #1, as suggested, integrating Eclipse or equivalent in SL.
LSL Wiki built into the editor
Detachable script editing window (To develop on one monitor & test
in the other)
Entity relationship diagram system in SL viewer for visual coding.
I'm not sure that spending whole lot of time adding fancy features
to the built in LSL editor is that productive (we aren't trying to
build an IDE, and there are a ton of really good extensible IDEs out
there already), but I really like your idea of putting together an
API. Someone could hack a service into the viewer that lets another
process (like Eclipse or Monodevelop) perform limited operations on
the inventory of the currently selected object.
We already have <http://www.freedesktop.org/wiki/Software/dbus>D-Bus
integration in the GNU/Linux Viewer for SLurl support, so it
shouldn't be too hard to expose something like an ObjectEditorProxy.
It could allow an extension for your favorite IDE to enumerate the
scripts that are editable in the currently selected object's
inventory, fetch their contents, compile(), and add new scripts to
the object's inventory. The IDE could also subscribe to events
emitted by the viewer, such as ScriptAdded, ScriptDeleted, etc.
What might improve the situation quite a bit is if the server
supported a capability that allowed the viewer to fetch all symbols
exported by the simulator (all LSL functions and constants). That
metadata could then be exposed to the IDE through the
ObjectEditorProxy for intellisense support.
In the long run I don't know if this is a good solution, but it
would certainly be an interesting experiment!
-Ambroff
_______________________________________________
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
