Difference between revisions of "Talk:LSL Portal To-do"

From Second Life Wiki
Jump to navigation Jump to search
(Creative Commons Image)
 
(22 intermediate revisions by 7 users not shown)
Line 1: Line 1:
:Is that necessary?  This is a wiki after all, the entire point is to just pick up something that needs to be done and do it, whenever the mood strikes. [[User:Gigs Taggart|Gigs Taggart]] 09:37, 25 January 2007 (PST)
<div style="float:right">__TOC__</div>
: Well, I know I'd be pretty miffed if I worked for hours on a function page, only to find out someone else already did it. It would be courteous to let others know whats being worked on to prevent duplicate efforts. [[User:Darien Caldwell|Darien Caldwell]] 10:11, 25 January 2007 (PST)
Removed old conversations. See: [https://wiki.secondlife.com/w/index.php?title=Talk:LSL_Portal_To-do&oldid=14812 https://wiki.secondlife.com/w/index.php?title=Talk:LSL_Portal_To-do&oldid=14812]
:: ...which is why you work on the page incrementally.  I strongly suggest working on only the lede of the article and then just posting it, with all the other sections blank.  Then edit each section individually to avoid edit conflicts like the kind you describe, and save it between every paragraph. (Don't worry, as far as I know, this does not waste disk space because of the way the wiki stores pages in the history.)
== Pointless ==
:: Besides, it is ''far'' too early to start working on the articles yet - the layout hasn't been agreed upon. For example, we need to construct an infobox for all the stats being added willy-nilly right now, like Energy cost and Sleep. At the very least, things need to be templatized so that we can flag articles as missing data or broken whenever we do something that ends up requiring changes or additions in all the other articles.  It'll get very very difficult to reformat things as more articles are created, especially if there's no way to keep track of progress.
:: I'm going to remove the table for now, but feel free to replace it if you have some other reason to want it.  (It's still in the history.) [[User:Celierra Darling|Celierra Darling]] 11:35, 25 January 2007 (PST)
:: One more thing: the table is currently split up on a bunch of other pages (most notably [[:Category:LSL Functions]], so there's no need for a huge to-do list here.  Just follow the red links.  If you'd rather look at the old list (just as a creation checklist, not as an "assignment" table!), see https://wiki.secondlife.com/w/index.php?title=LSL_Portal_To-do&oldid=6209 - I just wouldn't want to see pages start being "assigned" or even "claimed", since that can give people a very wrong idea. [[User:Celierra Darling|Celierra Darling]] 11:44, 25 January 2007 (PST)


(''table was removed'' - see https://wiki.secondlife.com/w/index.php?title=LSL_Portal_To-do&oldid=6209 to look at it)
This page is hopelessly out of date, I think if we want to keep it, it should be blanked and restarted with relevant information.  [[User:Gigs Taggart|Gigs Taggart]] 13:08, 4 March 2007 (PST)


: agreed it's a bit early to start working on articles, but the perfect time to iron these kinds of issues out. As long as I'm able to determine what's needed and what's already done, i'm happy :) [[User:Darien Caldwell|Darien Caldwell]] 12:18, 25 January 2007 (PST)
:I agree --[[User:Anthony Reisman|Anthony Reisman]] 15:11, 5 March 2007 (PST)


Yes, I do believe it is necessary. Some of the articles are very large, and I would like to edit them off-line, then upload them when I am ready. I don't want to spend a day on a long article, getting it just right, then try uploading it, only to find someone else has already uploaded something different. That's called duplication of effort, and it is a conflict and a waste. If we have something to let us know who is working on what, then we can minimize that. Since we don't have a way to track it (like a project tracker), that was the next best thing. So, unless you can come up with a better method of resolving this potential conflict, please put the table back. Thanks! [[User:Talarus Luan|Talarus Luan]] 12:53, 25 January 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. [[User:Strife Onizuka|Strife Onizuka]] 21:00, 5 March 2007 (PST)
:Also, though this is a Wiki, it would be polite if we discussed the removal of several hours' work before we actually did it. I know it is still in the history, but that's not the point. [[User:Talarus Luan|Talarus Luan]] 12:57, 25 January 2007 (PST)


== Settlement ==
== LSL Color-coding like wakka wiki? ==


If you choose to upload an article as one big upload, please put a note on the page that you intend to do so.
Should I add this to the to do list? [[User:Ina Centaur|Ina Centaur]] 02:29, 15 March 2007 (PDT)
:That is something LL needs to do. -- [[User:Strife Onizuka|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. --[[User:Meyermagic Salome|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.. ([[User:Ina Centaur|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). -- [[User:Strife Onizuka|Strife Onizuka]] 17:38, 1 May 2007 (PDT)


"I will be uploading this page as a complete article shortly, editing it now is likely futile <nowiki>~~~~</nowiki>"
== need for https(?) ==


We will have to be watchful for any of these that stick around too long.
Is there actually a need for the https protocol to be used on this wiki? (Not even wikipedia, MediaWiki's flagship implementation, uses https...) ([[User:Ina Centaur|Ina Centaur]] 16:35, 1 May 2007 (PDT))


The agreement is that the people that want to do incremental editing can do incremental editing, and the ones that want to do full uploads can do full uploads. We have to be a little careful to not let these two styles clash, but the big rule is:
:You should ask this question again on [[Talk:Main_Page]] it doesn't belong on this page. -- [[User:Strife Onizuka|Strife Onizuka]] 17:36, 1 May 2007 (PDT)


'''NO WHINING!'''
== LSL Wish List ==


If an edit improves a page, even if it wiped out your half completed page, you'll get no sympathy from whining about it.  Merge your content in from the history if you had any unique content that isn't covered in the new version.
Tanya prays to the code-gods and rubs her little 6-bit lamp...
<ul>
<li> a <b>switch</b> for casing
<li> ability to call a function from a list of string variable names
</ul>


We are a small group here, so we can settle things without any edit wars or other silliness. [[User:Gigs Taggart|Gigs Taggart]] 18:48, 25 January 2007 (PST)
<lsl>


== Creative Commons Image ==
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;
    }
}


Fix the template so that when users are logged it, they will get warnings that the creative commons logo is not connected via a secure link.  We just need to switch to hosting that file on the this server, and use a absolute path to the file, http://creativecommons.org/images/public/somerights20.png  It starting with http in the template is what's causing the warning. [[Kunnis Basiat]]
</lsl>
<p>
<lsl>


list func_list=["do_this","do_that","do_whatever"];


:That file is part of the site skin, you will need to post a web bug at [http://jira.secondlife.com SecondLife Jira Site]
do_this(list params) {
--[[User:Thraxis Epsilon|Thraxis Epsilon]] 19:25, 25 January 2007 (PST)
  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>
 
----[[User:Tanya Avon|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. -- '''[[User:Strife_Onizuka|Strife]]''' <sup><small>([[User talk:Strife_Onizuka|talk]]|[[Special:Contributions/Strife_Onizuka|contribs]])</small></sup> 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 <b>switch</b> block internally could save a lot of memory using a hash/call at low level. ----[[User:Tanya Avon|Tanya Avon]] 13:53, 11 September 2012 (PDT)

Latest revision as of 16:46, 11 September 2012

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)