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)