Talk:LSL Portal To-do

From Second Life Wiki
Jump to: navigation, search

Removed old conversations. See: https://wiki.secondlife.com/w/index.php?title=Talk:LSL_Portal_To-do&oldid=14812

Pointless

This page is hopelessly out of date, I think if we want to keep it, it should be blanked and restarted with relevant information. Gigs Taggart 13:08, 4 March 2007 (PST)

I agree --Anthony Reisman 15:11, 5 March 2007 (PST)
I'm more into doing work then talking about doing it. I've not used the page for anything other then to tell everyone what works needs to be done. Strife Onizuka 21:00, 5 March 2007 (PST)

LSL Color-coding like wakka wiki?

Should I add this to the to do list? Ina Centaur 02:29, 15 March 2007 (PDT)

That is something LL needs to do. -- Strife Onizuka 02:41, 15 March 2007 (PDT)
There is a GeSHi plugin for Media Wiki, and I could modify GeSHi's PHP syntax file to fit LSL with fairly little effort, but yes, LL still needs to do the actual additions. --Meyermagic Salome 17:56, 14 April 2007 (PDT)
Yes, I heard about the various color-coding addons for MediaWiki at HD in the last WikiMania. Amazed none has been implemented yet.. (Ina Centaur 16:37, 1 May 2007 (PDT))
It's been a while since anyone has put pressure on LL to implement this. Considering the current climate I wouldn't press this issue (they have enough thing on their plate). -- Strife Onizuka 17:38, 1 May 2007 (PDT)

need for https(?)

Is there actually a need for the https protocol to be used on this wiki? (Not even wikipedia, MediaWiki's flagship implementation, uses https...) (Ina Centaur 16:35, 1 May 2007 (PDT))

You should ask this question again on Talk:Main_Page it doesn't belong on this page. -- Strife Onizuka 17:36, 1 May 2007 (PDT)

LSL Wish List

Tanya prays to the code-gods and rubs her little 6-bit lamp...

  • a switch for casing
  • ability to call a function from a list of string variable names

<lsl>

func(integer x) {
    switch(x) {
       case 0:
          llSay(0,"Borked");
          break;
       case 1:
          llSay(0,"Grid");
          break;
       case 2:
          llSay(0,"Foobar");
          break;
      default:
          llSay(0,"Unknown");
          break;
    }
}

</lsl>

<lsl> list func_list=["do_this","do_that","do_whatever"]; do_this(list params) { llSay(0,"Doing this."); if (llList2String(params,0)=="param") llOwnSay("hoorah"); } do_that(list params) { llSay(0,"Doing that."); } do_whatever(list params) { llSay(0,"Fooing bar."); } default { state_entry() { llListCall(func_list,0,["param","params","others"]); } } </lsl>


Tanya Avon 16:12, 10 September 2012 (PDT)
Switch statement is doable without a large amount of work. "eval" like function would be a huge amount of work. -- Strife (talk|contribs) 21:28, 10 September 2012 (PDT)
Could you give an example? Right now... if i have over 100 various menu options to parse, i typically do something like this....

<lsl> if (var!=0) {

   if (var!=1) {
       if (var!=2) {
           if (var!=3) {
               llOwnerSay("Error: var:"+(string)var+" "+llGetScriptName());
           } else pick_nose();
       } else play_tunes();
   } else send_card();

} else init_foo();

</lsl> with only 3 or 4 cases, its not a big deal, but seriously, i do have scripts that have well over 100 cases to parse. It costs me an entire script to do that and it will utilize

link messages to handle all the menu options. A good switch block internally could save a lot of memory using a hash/call at low level. ----Tanya Avon 13:53, 11 September 2012 (PDT)