Comments on: Scripters : Object Name and Description Changes http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/ By Linden Lab Sun, 20 Jul 2008 20:02:14 +0000 http://wordpress.org/?v=MU By: After the 1st February blues « Ananke Media Systems http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-606021 After the 1st February blues « Ananke Media Systems Tue, 13 May 2008 11:00:24 +0000 http://lindenlab.wordpress.com/?p=1605#comment-606021 [...] stop working, you absolutely need to let people know in advance. It is a shame that this change was documented by Linden Lab after the fact rather than days or weeks in advance. If Linden Lab had announced this change in advance, [...] [...] stop working, you absolutely need to let people know in advance. It is a shame that this change was documented by Linden Lab after the fact rather than days or weeks in advance. If Linden Lab had announced this change in advance, [...]

]]> By: Yacobheimer125 Voom http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-590075 Yacobheimer125 Voom Thu, 13 Mar 2008 01:41:26 +0000 http://lindenlab.wordpress.com/?p=1605#comment-590075 Of course, they have to be careful so people don't start making chat loggers..... Too bad though - saving to memory would be a great addition to LSL. Of course, they have to be careful so people don’t start making chat loggers…..
Too bad though - saving to memory would be a great addition to LSL.

]]> By: B. Shinobu http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-588066 B. Shinobu Wed, 05 Mar 2008 12:45:59 +0000 http://lindenlab.wordpress.com/?p=1605#comment-588066 The idea I posted above has now been JIRAed. http://jira.secondlife.com/browse/SVC-1754 The idea I posted above has now been JIRAed.

http://jira.secondlife.com/browse/SVC-1754

]]> By: B. Shinobu http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-588060 B. Shinobu Wed, 05 Mar 2008 12:02:11 +0000 http://lindenlab.wordpress.com/?p=1605#comment-588060 I script in SL, and I do use the name and description fields as a data-storage. Fortunately, most of my scripts don't use anything excessively long, but LL has severely limited its use as a data storage possibility. My sentiments have been echoed by many, even most, of the people who have written here, in that we need persistent data storage. Personally, I'm more concerned about that than I am about mono. I would also like to re-suggest a very plausible idea that someone else mentioned, and which I've actually thought of before, along with several other scripter friends of mine: an llGetText() function to retrieve the text stored in the floating text parameter of a prim. It's already in existence, it has 255 chars of available storage space, and 255*255 = 65025 chars of storable information. Plenty for a "quick fix" as it was called. It doesn't change over rezzes, is copied along with the prim, and all in all is a perfect candidate until an actual information storage property becomes available. I script in SL, and I do use the name and description fields as a data-storage. Fortunately, most of my scripts don’t use anything excessively long, but LL has severely limited its use as a data storage possibility. My sentiments have been echoed by many, even most, of the people who have written here, in that we need persistent data storage. Personally, I’m more concerned about that than I am about mono. I would also like to re-suggest a very plausible idea that someone else mentioned, and which I’ve actually thought of before, along with several other scripter friends of mine: an llGetText() function to retrieve the text stored in the floating text parameter of a prim. It’s already in existence, it has 255 chars of available storage space, and 255*255 = 65025 chars of storable information. Plenty for a “quick fix” as it was called. It doesn’t change over rezzes, is copied along with the prim, and all in all is a perfect candidate until an actual information storage property becomes available.

]]> By: Bucky Barkley http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-587014 Bucky Barkley Mon, 25 Feb 2008 18:01:14 +0000 http://lindenlab.wordpress.com/?p=1605#comment-587014 What is really needed is llGetInventoryDesc(), which would allow for inventory names to be treated as keys, and descriptions as values. Vote for https://jira.secondlife.com/browse/SVC-377 What is really needed is llGetInventoryDesc(), which would allow for inventory names to be treated as keys, and descriptions as values.

Vote for https://jira.secondlife.com/browse/SVC-377

]]> By: Anna Tretiak http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-586774 Anna Tretiak Sat, 23 Feb 2008 10:49:34 +0000 http://lindenlab.wordpress.com/?p=1605#comment-586774 Prospero @17: You say that the pipe character was "supposed" to be avoided. What do you mean by that? Was that documented anywhere? It would be nice if you guys could provide a comprehensive, stable and serious set of documentation for LSL, including limitations like that, rather than letting us LSL *users* to reverse engineer the language and create the documentation ourselves. Never in my 20 years of professional software engineering practice I have seen such a nonsensical approach. Also, why can't the pipe be used? Any decent database system is able to store *any* character into a text field. You only need to escape it appropriately when embedding it in code. That thing with the forbidden characters is jurassic. Prospero @17: You say that the pipe character was “supposed” to be avoided. What do you mean by that? Was that documented anywhere? It would be nice if you guys could provide a comprehensive, stable and serious set of documentation for LSL, including limitations like that, rather than letting us LSL *users* to reverse engineer the language and create the documentation ourselves. Never in my 20 years of professional software engineering practice I have seen such a nonsensical approach.

Also, why can’t the pipe be used? Any decent database system is able to store *any* character into a text field. You only need to escape it appropriately when embedding it in code. That thing with the forbidden characters is jurassic.

]]> By: Anatag Paperclip http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-585901 Anatag Paperclip Sun, 17 Feb 2008 10:54:35 +0000 http://lindenlab.wordpress.com/?p=1605#comment-585901 I am just learning scripting for SL. I am absolutely gobsmacked that there is no persistent storage. LL are making the reflections off water look nice but not allow objects to have state? SL is a toy. I am just learning scripting for SL. I am absolutely gobsmacked that there is no persistent storage. LL are making the reflections off water look nice but not allow objects to have state? SL is a toy.

]]> By: Notecard Writing: A Modest Proposal « Evans Avenue Exit http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-584693 Notecard Writing: A Modest Proposal « Evans Avenue Exit Mon, 11 Feb 2008 07:22:31 +0000 http://lindenlab.wordpress.com/?p=1605#comment-584693 [...] scripters have used the object name or description to store such persistent data, but the fact that LL is now enforcing strict limits on the length of those fields limits the usability of this technique.) We are told that this is because each edit to a notecard [...] [...] scripters have used the object name or description to store such persistent data, but the fact that LL is now enforcing strict limits on the length of those fields limits the usability of this technique.) We are told that this is because each edit to a notecard [...]

]]> By: Tormented Twilight http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-584346 Tormented Twilight Sat, 09 Feb 2008 00:02:49 +0000 http://lindenlab.wordpress.com/?p=1605#comment-584346 Hey! Your bugs no longer work! We're Mad! Rawr! ^ _ ^ Hey! Your bugs no longer work! We’re Mad! Rawr!

^ _ ^

]]> By: Nibb Tardis http://blog.secondlife.com/2008/02/01/scripters-object-name-and-description-changes/#comment-584333 Nibb Tardis Fri, 08 Feb 2008 22:55:00 +0000 http://lindenlab.wordpress.com/?p=1605#comment-584333 I fail to understand why, in this day and age, characters such as "|" are considered illegal. Why do simple things such as the script editor, object names and descriptions still not support international characters ? So the pipe character was broken, but why did LL choose to disable it altogether instead of actually fixing names and dscriptions to support more than plain ASCII characters ? I fail to understand why, in this day and age, characters such as “|” are considered illegal. Why do simple things such as the script editor, object names and descriptions still not support international characters ?

So the pipe character was broken, but why did LL choose to disable it altogether instead of actually fixing names and dscriptions to support more than plain ASCII characters ?

]]>