User talk:Darien Caldwell

URL(En|De)code

I like your idea of referencing similar functions from other languages. Maybe an optional collapsible table (collapsed by default) in the Summary section with function names as links for the other languages? An added bonus of this feature is that it would allow people to search the documentation for LSL functionality based on the names from other languages. Thoughts? -- Strife ^{(talk|contribs)} 13:23, 23 August 2012 (PDT)

Yes I don't think it needs to be prominent. You hit upon the exact idea behind it, as every time I want to find the two functions mentioned, I'm always looking for llURLEncode() llURLDecode(), It's just exactly what I expect from other languages. Then I spend a lot of time trying to remember what LL calls them. I figured referencing the common function name would help people like me who often confuse with other languages. So I think your idea is a fine one. Darien Caldwell 22:43, 23 August 2012 (PDT)

I don't have a good idea as to how this should be templatized (not to mention the entire template & information sprawl issue does gnaw upon me, and I don't have a good solution for that, and I'm sorry for it). I'm thinking includable subtemplates like the Signature section. Has potential, I'll do a mockup tomorrow (or when I have time). -- Strife ^{(talk|contribs)} 23:00, 23 August 2012 (PDT)

Take a gander at Template:LSL_Other_Languages. I'll transclude it when if you think it's ready. Do you think it's important that this is in the Summary section? From a users perspective knowing it's similar to a function you already know really speeds up learning about it, but only if you know of the function. So having the most popular alternate names visible helps, but having the full table of names does does not. It should be compact and informative at the same time. As a stop gap solution, it is currently showing the first three other function names in the text. -- Strife ^{(talk|contribs)} 09:22, 24 August 2012 (PDT)

To answer my own question, yes I think it's important enough to be in the summary section. -- Strife ^{(talk|contribs)} 09:30, 24 August 2012 (PDT)

Yes I think that's perfect. As long as the search can index the whole table, showing only a few makes sense. Ship it, I say. :) Darien Caldwell 11:11, 24 August 2012 (PDT)

PRIM_LINK_TARGET

I didn't know you could use PRIM_LINK_TARGET with llGetPrimitiveParams. That is cool. -- Strife ^{(talk|contribs)} 20:54, 28 August 2012 (PDT)

Yeah i needed it today, and wasn't sure myself. But it worked. :) Darien Caldwell 00:13, 29 August 2012 (PDT)

Animation Length Limit Update

Thank you for your update to the Animation Length Limit article I wrote. I wrote several articles linked in Talk:How to create animations. I still keep an eye on them. I hope no others are out of date.

I hope someday all the bugs with the animation system will be fixed, and someone will update the information on that. I even submitted patches for some, but to my knowledge, they are still unapplied.

Coaldust Numbers 05:43, 30 June 2013 (PDT)

Template:LSL Constants/ReturnError

I don't know what I was channeling when I wrote those descriptions. With ERR_GENERIC, I think I started channeling Zork. Which lead me to lookup and then recompose some of the haiku that you will find in the HTML comments in the table. I'm thinking about writing one for each constant. Does that make me insane? -- Strife ^{(talk|contribs)} 22:02, 9 July 2013 (PDT)

LOL, I think it just means you have a sense of humor. :) I shall have to peruse these works. Are you sure you saved it? The template seems to be unmodified, even from source view.Darien Caldwell 18:12, 10 July 2013 (PDT)

SVC-7987

Good catch! I've redefined look_at for both teleport functions to be directions. -- Strife ^{(talk|contribs)} 18:15, 12 March 2016 (PST)