Why reinventing the wheel ?
Henri Beauchamp
You know, it has been
years
that I implemented Lua scripting in the Cool VL Viewer, with automation features (based on Lua callbacks for the various events happening in the viewer or in world), UI customizations (you can design your own Lua floaters if you want), Lua threading support (better than coroutines since they do not impact the viewer main thread as much as the latter), Lua and LSL interaction (and Lua and D-Bus interaction too, under Linux) etc...Granted, my viewer is very different from LL's, but most of what I implemented for Lua could be backported to LL's code base (and all TPVs deriving from it).
The full documentation for my implementation is available here: http://sldev.free.fr/CoolVLViewerLuaManual.pdf
Log In
Coaldust Numbers
I am voting this up because I want Linden Labs to at least thoroughly examine a preexisting attempt so that whatever they make will be better informed. I also appreciate the effort already exerted.
I do not mean to imply that I do not want them to make any changes. For example, I would expect them to add much better integration with in-world objects and avatars.
And there is the matter of in-world Lua scripting that viewers cannot add themselves.
NaomiLocket Resident
Or at least say why, different implementation features? Missing desired implementation features?
Henri Beauchamp
NaomiLocket Resident
Because: "not made by LL"... :-(
Gwyneth Llewelyn
Henri Beauchamp thanks for piping in — I was thinking about that when I saw this board and wondered if something had happened to the Lua implementation on the CoolVLViewer :)
I totally agree, it's stupid to reinvent the wheel when
all the hard work has already been done
(and tested!!!). I hope that at least LL takes that in consideration — taking into account the many other differences between the viewers, of course.