what kinda code is used?

what code do u guys use? VB? C? C++?

lsl

(sorry)

A legitimate question requires a legitimate anser. Check out:
http://secondlife.com/badgeo/wakka.php?wakka=HomePage

On big projects I use ESL (Extended LSL) which compiles to LSL. Just fineshed a huge project in ESL.

Tell us more!

Well it was a script set for a private 3rd party (who will not be named) that extensively used the TLML (TightList Markup Language) 0.70 beta and the alpha version of TLWAPI (TightList Window API). TLWAPI is part of roadmap for TLML 1.0

TLWAPI is still under heavy development (the core is stable but the actual API is in flux). I'm currently working to get TLML to a 1.0 status; cleaning out old code from the TLTP era (TLML 1.0 will not be compatible with TLTP; the 0.70 beta maintains compatability).

Layer 0 is TLML itself, the raw prims.
Layer 1 is TLWAPI
Layer 2 are extensions to TLWAPI adding higher level controls.
Layer 5 User scripts.

TLWAPI does 3 task.

1. Allocate and de-allocate prims dynamicly
   
2. Virtual Hierarchical Linking
   
3. TLWAPI comands
   1. Raw TLML Allocate (allocate prims and send them TLML commands)
      
   2. Path Deallocate (deallocate a single prim by it's path or multiple prims in a path)
      
   3. TLML command proxy, allows commands to be sent to a path without being sent to every prim in the set (for complex objects this is a plus).
      
   4. Specialized Allocation
      1. TextDot (floating text)
         
      2. XyTextMod (dynamic length or static & multi lined with configurable path building)
         
      3. Button (simple box with texturable faces)
         
      
      
   
   

The TLWAPI hierarchical tree (used for deallocation & proxy commands) is very tight on memory; Using 2 bytes per prim, can support up to 1024 prims (though you cannot link that many together). TLWAPI keeps a stack of available prims, (at script boot it builds this stack), the stack is FIFO, as prims are deallocated they are placed on the end of the stack. The way the hierarchial tree is stored it is fast to deallocate and send proxy commands. There are 3 characters that cannot be used in path names "|", "=", "," they are used as internal seperators; using them will caused leaked memory in the tree.

I'm planning a few Layer 2 extensions to TLWAPI. The first being Views, where you can feed it a strided list of data for which it will build a TLML command and update the view with that data.

The main reasoning for the Views extension is that doing it manually is very compilicated; it takes up huge amounts of script memory (bytecode size). In my recent project, I had both interface update code and a complete comms in a single script; the result was a script that was very tight on memory. Offloading it would have saved me time (optimizing a script for bytecode can take days of debugging and reoptimizing).

TLTP interfaces directly with Layer 0. It doesn't do prim allocation in a nice mannor. The script project I mentioned worked mostly by sending TLWAPI commands (and a few TLML commands directly to update prims where the link number was known). In the future TLTP may be re-added as a Layer 2 script; which should solve it's allocation problems. Aspects of TLTP will be lost.

The fancy allocation functions may migrate to Layer 2. Or extended via Layer 2 rewrites.

TLWAPI is writen entirely in ESL, and has an Include that makes writing TLWAPI commands easy via macros.

When all was done and told, on my project i mentioned before; it had 50 different link message comms.

Sounds like a lot of abstraction. What are some of the features / practical applications of such a design?

Also, what/where is ESL? (Yeah, I know what it means, but what is it specifically).

Sounds a bit like a framework for prim based HUD GUIS et. al. if something like that can be really pulled out of lsl and a basic prim lib.
Will it be off for licence or rather open source (copy but no mod) in a limited version of a limited number of prims?
Or is this a joke?

Regards,
Leff.

ESL support currently is only provided by Scite - Ez. A useful tool to add into your building is lslint; which does syntax checking.

lslint thread
SciTe-ez thread
First ESL thread

The project I was using TLWAPI with was a HUD to make nice window interfaces. In the sim where we were testing it, the interface was quite quick (it did caused the IPS to jump). TLWAPI will be OpenSource and free to use. Probably will be released under Lesser GNU Public License.