Create a script writable script version number
closed
BluesToday Resident
Currently, I try to track script versions by manually updating the script description (not the script name as recommended here: https://wiki.secondlife.com/wiki/LSL_101/Creating_a_Script). Updating the script name or description is tedious and error prone (and changing the name of the object with llSetObjectName () adds other complications, not least having llListen() being able to target an object by name).
I have an automated script build pipeline that generates version numbers that I use for both scripts and objects contained in a single repository. It uses the C preprocessor to finagle a #define VERSION statement into the LSL that is then loaded into the object's description in the state_entry event in the default state.
However, this is far from perfect as the object description (or name) is associated with the object, not the script. Worse, there may be multiple scripts in an object that have different version numbers.
It would be nice if there was a script writable field associated with the script that you could write to from the script, similar to llSetObjectDesc (). Failing a specific field dedicated to a version number, let us write to the script's description field by adding a function llSetScriptDesc ().
Log In
Maestro Linden
closed
Hello, and thank you for your feature request.
Incoming suggestions are reviewed in the order they are received by a team of Lindens with diverse areas of expertise. We consider a number of factors: Is this change possible? Will it increase lag? Will it break existing content? Is it likely that the number of residents using this feature will justify the time to develop it? This wiki page further describes the reasoning we use: Feature Requests
This particular suggestion, unfortunately, cannot be tackled at this time. However, we regularly review previously deferred suggestions when circumstances change or resources become available.
We are grateful for the time you took to submit this feature request. We hope that you are not discouraged from submitting others in the future. Many excellent ideas to improve Second Life come from you, our residents. We can’t do it alone.
Thank you for your continued commitment to Second Life.
Woolfyy Resident
On my side i have a more dynamic use of numbering of scripts sources with at the same time numbers that i increment and letters that i use to point out a certain feature that i am updating. So let's say that no automatic numbering could fit to such needs :-) I can also mix it with a date to know what is the modification date of some data, that can happen later depending on configuration, with updates being done in parallel of generations of scripts.
Moreover i use pre processor features to configure a script depending on which build i use it inside, which is a feature that is only possible with Firestorm ... but it s a good way to have global scripts whose behavior can be different depending on the build in which they are injected.
As for the description field in builds, i use them to point out to prims that i use as containers for some features that are detected by cascading supervisor scripts ...
etc etc etc this is just to say that needs depend on use and how we architecture our development systems, knowing too that on my side i don't use any script stored outside SL as it always end up unreliable one day or the other.
Once said, the best way is certainly to go on the way each one is used to ...
Daemonika Nightfire
I dont know why it was not listed on the funktions page.
LG
Dae
Woolfyy Resident
Daemonika Nightfire it is a function recently added https://feedback.secondlife.com/scripting-features/p/add-llgetinventorydesc-function
Peter Stindberg
A 'llSetScriptName' function would come in
very
handy.BluesToday Resident
@Peter Stindberg: Changing inventory names is already covered here: https://feedback.secondlife.com/scripting-features/p/function-to-change-set-inventory-item-names. I'd prefer something that is explicit to versions, failing that, let me set a version string in the description (although setting description is a workaround in my opinion).
Peter Stindberg
BluesToday Resident Every dev has their version numbering scheme, from "none" to V1/V2/V3 to the xx.yy.zz most of us use, to other wild things. So if you don't want the Lab to push a versioning scheme onto us, your suggested field would have to be a text field. I see some redundancy there and still think being able to change a scripts own name by script is the more versatile solution.
Peter Stindberg
But by all means, a seperate field would be better than nothing!
BluesToday Resident
Peter Stindberg Yes, it would need to be a text field which is why my alternative to a dedicated field is the script's description. I
really
dislike renaming scripts. What if you need to do a llResetOtherScript ()? You've just added the complication of finding out the script name. However, as I mentioned, renaming inventory is a tracked feature request, so if you want to rename, I won't stop you :)Peter Stindberg
BluesToday ResidentOhhhh, good point about llResetOtherScript!