Batch uploading of LSL sourcecode

I propose that LL implement a way to batch upload lsl sourcecode files, much like we can batch upload textures, animations and sounds. Each is compiled by the client before it is uploaded. If compilation fails on one of the files, it is opened in a script window.

This would greatly ease the burden on people who like editing projects offline. Large projects using tools like CVS for collaboration and maintenance would also greatly benifet.

(Proposal 853)
Discuss away
==Chris

Hi there, Christopher Omega.

I'd like to suggest that the process work both ways - add to your idea being able to copy LSL files from inworld to your hard drive in batch form, possibly something like right clicking a folder in your inventory and having an option to copy all the scripts contained therein into a folder on your hard drive.

I've got at least 200 short LSL scripts in my inventory that I would like to merge into one big text file so that a person wanting sample usage of any LSL function or keyword or constant could just load this big text file into notepad or any text editor and do a find for the term and there it would be in, in the context of a working script. But copying and pasting the text is too much bother given that I would get zero pay for doing it.

If there has to be a charge for this it should be very low. Not 10 lindens per script.

Have just voted on this. Support this concept.

From my angle, ideally the ability to be able to have your "source of reference" code on one's PC (in CVS, subversion whatever) and the ability to build/deploy this in an automated sense. For example if script A is used multiple times you really only want to update it once, run lslint to check it, then say DEPLOY and have it automatically deployed into all prims/objects that have that script. There would need to be a mapping file potentially to handle versions. But utlimately if we want to offer developers something that just somewhat resembles development best practice we shoudl strive for this.

Also ultimately a scriptlet TAG approach for embedding common sections of LSL code across multiple scripts, but only maintaining it in one place.

Sorry - I'm going overboard, but I see this request as taking a step in the right direction.

Cheers

You can almost do this today, using the existing toolset.

Edit your code on your local PC, and then email it to a code management prim. That would have a script that parses the file for the destination prim ("// CODE MGR my_prim this_script" and uses llLoadRemoteScriptPIN() to update the script.

A sohpisticated enough editor PC-side would let you set up a one-key macro to lslint your file, package it, and email it off.

Really - I don't quite see how you have a string (representing the script contents) and use this to update a script via llRemoteLoadScriptPin(). Doesn't this require an existing inventory script? i.e. the problem is how to create an script in an inventory somewhere from a chunk of script text in a string?