What I'm working on now:

08/16/2006

Well, there are a couple of things I've been wanting to get done, and it looks like I have some free cycles coming up, so I'm gonna try to knock them out.

1) PHP library of classes for interaction with LSL - This means getting all (or at least most of) the LSL constants exposed in a PHP class, writing methods to enable serialization of data to LSL types, writing classes representing each LSL type, etc. I've made some progress on this already, and I'm not going to wait too long before releasing this into the wild...it'll probably be one of those things that's never actually "ready" so I figure I should just get it out there.

The serialization code is being derived from LSL code that ReadyJack and Strife Onizuka (BlindWanderer) have provided on the wiki. I'll be providing the LSL-side serialization code when it's ready (same time as the PHP stuff, I suppose). -Update I just put the LSL serialization code up at LibrarySerialize

2) LSL library wrapping HTTP functionality - I'm very excited about having HTTP available now, but it's still pretty painful for extensive usage....one example is the character limit on llEncodeURL(), which just KILLS me. The idea of the library is to provide code that "breaks" the traditional notions of POSTed form data but does so in a uniform way. This is pretty much a hack around the llEncodeURL() crap. I'm also probably going to include wrappers for interacting with the PHP library in this.

3) Dynamic object creation via the web. The idea here is to build upon the awesome work that Jason Gomez has done with his Blender-based prim builder and use the same XML schema to store prims online. The webserver would then provided a) a management interface for objects and b) a streamlined mechanism for conveying the prim data to an in-world prim importer. The importer implementation I've seen thus far relies on a notecard and parses the xml using LSL. I want to take a different approach. I'll be transmitting a stream of serialized data to the importer, and it will be able to very easily (and, hopefully, quickly) pass that along to the dynamic prims.

4) Stop using split infinitives

So stay tuned....