Omega Point

The LSL Wiki finds a new home

After a cou­ple months of fight­ing to retrieve data from my ISP, argu­ing about whether or not I had the right to trans­fer the LSLwiki.com domain name — and finally buy­ing a new one — fol­lowed by a cou­ple days’ worth of mess­ing about with MySQL, I’m pleased to say the LSL Wiki has returned, in editable, “cur­rent” form. Your old logins and pass­words work.

Every­thing is the way it was at the moment the wiki went down. Nothing’s changed, we just wanted to get an editable wiki back up, but we have some fixes and addons to be rolled out over the next cou­ple of weeks.

One catch though: this time, it’s at LSLwiki.net. I’ve put up redi­rects at the old site at LSLwiki.com, but it remains to be seen whether or not I’ll ever be able to recover that domain and put it to more use­ful… use.

This announce­ment comes right on the heels of Milo Linden’s “ohhh yeah­hhh…” forum post:

Cur­rently on the aditi beta grid.

llSetLinkTexture(integer link_pos, string tex­ture, inte­ger face)
Sets the tex­ture of face for link_pos

llSetLinkPrimitiveParams(integer linknum­ber, list rules)
Set prim­i­tive para­me­ters for linknum­ber based on rules.

Yes! It’s about time! (By which I mean, “thank you for the con­tin­ued steady ful­fill­ment of the userbase’s most desired wishes, Lin­den Lab.”) These are two of the biggest “miss­ing func­tions” in LSL. With their addi­tion, scripters can update all prims in an object with one script instead of a hun­dred or more.

Now, let’s get to work updat­ing this thing!

LSL Wiki back up at LSLwiki.com

It’s true, the LSL Wiki has returned, now hosted at LSLwiki.com. This is the com­plete data­base as it existed on SecondLife.com as of the moment it was taken down. Your logins are all the same. There’s still a cou­ple redi­rect prob­lems I haven’t cleaned out yet, but it works. I’ll fin­ish fix­ing that stuff tomor­row. In the mean­time, happy LSLing.

Edit: There will be changes and upgrades to the wiki in the near future. Some of this may include port­ing the data­base to a more mod­ern wiki engine. I’m cer­tainly not mak­ing this deci­sion alone, but I haven’t decided what I want to do yet.

LSL Wiki relocating

Due to the recent secu­rity issues affect­ing Sec­ond Life, the LSL Wiki will no longer be hosted on the Sec­ond Life web­site I’ll post addi­tional updates here next week when it relo­cates to its new home at LSLwiki.com.

In the mean­time, a few users have a backup avail­able here.

And we’re back!

I’ve noted on sev­eral occas­sions that I only ever get to upgrade my com­puter when some­thing very bad hap­pens to it and I have to replace parts. This tends to hap­pen once or twice a year, in my expe­ri­ence. As such, my desk­top has now made the jump to PCI Express video — to my annoy­ance. While I can’t help but be impressed by the increased per­for­mance, I also can’t help but be annoyed that I was forced to do this at all.

Regard­less, I am back for good this time. Really.

In my absence, it seems there’s been some long-awaited changes to the group tools, a topic I’m very eager to talk about shortly.

In LSL news, the changed() event has been fixed to han­dle cases in which a script is dropped on an object, as has llGetScript­Name. Addi­tional bugs have been dis­cov­ered in changed() as well, lend­ing fur­ther cre­dence to my the­ory that it’s actu­ally been an elab­o­rate hoax on the part of Cory Lin­den all along. This time, it’s been the tele­port and region-crossing detec­tion func­tion­al­ity that’s bro­ken. Scripters, make sure you put your essen­tial scripts in root prims!

Miguel de Icaza on the LSL-to-Mono port

Mono project founder Miguel de Icaza writes about Lin­den Lab’s pre­sen­ta­tion at Lang.NET 2006 in which Cory and Bab­bage Lin­den described the upcom­ing move to the Mono CLI.

The chal­lenge is to stop and save a run­ning script. This is some­thing that is rel­a­tively easy done with their script­ing lan­guage, but it becomes trick­ier with the CLI.

Their imple­men­ta­tion instru­ments the gen­er­ated CIL assem­bly to allow any script to sus­pend itself and resume exe­cu­tion on demand. This is a bit like con­tin­u­a­tions, the main dif­fer­ence is that the script does not con­trol when it is sus­pended, the run­time does. The instru­men­ta­tion basi­cally checks on every back-branch and on every call site whether the script should stop (in Jim’s words, “even­tu­ally, you run out of method, or you run out of stack”) and if it must stop, it jumps to the end of the method where a lit­tle stub has been injected that saves the state in a helper class and returns.

A very clever idea. Hope­fully the slides for the pre­sen­ta­tion will be posted soon.

I’d very much like to have attended that pre­sen­ta­tion, and I’d be inter­ested in see­ing those slides as well.

Fol­low­ing my attorney’s advise I have obtained a Sec­ond Life account.

Wel­come to Sec­ond Life, Miguel!

(Link stolen from Baba Sucks.)