LSL requests

Some of these may have been mentioned before, but decided that it wouldn't hurt to sling 'em at the Linden's again:

1. strings should be indexable via bracket operators; e.g., foo[2] yields third string character
   
2. lists should be able to contain lists
   
3. have an associative container
   
4. have true object-oriented behavior; e.g., it'd be nice to be able to write, say, a landmark sub-class that can be used to teleport avatars to landmark location; 'sides it'd be nice to get away from C-isms
   

Cheers,

Piprrr

Land information retrieval functions.

In the LSL script editor, PLEASE move the 'Undo Changes' button away from the 'Save' button.

I can't tell you how many times have I had a last-second wrist spasm and clicked Undo instead of Save? lol

-- forall x in list do blah
-- eval()
-- llParseNotecard2List

Here is my list...

llList2Notecard
llNotecard2List (with asynchronous event)
Draw text on a prim face

Chil, chill. They are very busy right now with Havoc 2. I'm sure it's causing havoc on their time. We can always repeat this again later.

Yes, but "waiting until the Lindens have time" isn't what this forum is for. "Talking about ideas for features" is.

The Lindens will always be busy. That's their job. Ours (at least in this forum) is to throw out ideas and critique them, then attempt to build up interest among the

My suggestions?
1. Better camera functions in LSL. I want to be able to have a script set camera position, target position, zoom, FOV, camera rotation, and then be able to change them all without having to get up or reset controls or anything like that. There are a bunch of people either working on machinima projects, or who would like to work on one. Better camera functions would mean better quality films.

Providing better machinima tools could potentially mean more free advertising. Look at the success of Red vs Blue.

2. Invisible mode! Please! I want to be in the world, visible to all, with a name over my head, a green dot on the map, and visible to sensors, I just don't want to be in the "Online users" list if I so choose.

3. As Hank said, text on a prim face. Client-side texture baking from XML input would be very convenient and would reduce the amount of data required to send to the client.

Thank you, that was pretty much my intent. Moreover, as a developer it's very easy to be so immersed in designing and programming that it's easy to lose sight of "use case scenarios" that mean a lot to the user. Therefore providing unprompted feedback is important to not only let them know of desired unimplemented use case scenarios, but also of poorly implemented ones.



Sounds good to me!



This is an excellent, and important, point. Think of this as "word-of-mouth" advertising, but with movies.


What kind of problem is this trying to solve? Is harrassment really that commonplace?



I'll not only second that, but extend it.

One of my frustrations is with texture manipulation and editing. It's very difficult to create a texture that maps just right in Second Life. The edit/upload/retry cycle becomes tedious and gobbles Linden bucks. It would be nice to have some texture editing functions. E.g.:

1. query color at a point
   
2. change color at a point
   
3. gaussian blur
   
4. single facet image mosaicing, thereby "allowing" more than one texture on a single facet
   
5. other image processing functions such as clipping, applying filters, etc
   

The first two I think are very important. The rest is just idle wishful thinking. (And can be re-implemented if the first two were available.)

Here's a use case scenario for you:

One of the problems with Second Life is that most objects look too clean. In RL, things are dusty, dirty, grimy, scraped, dinged, and singed, among other abuses. I'd like to be able to upload a basic texture for, say, a piece of metal. I'd then apply that texture to a surface. I'd then run a script that would modify pixels to make the surface look rusty.

User              System
_________________________________
Uploads           Texture stored
texture           in inventory

Applies           Surface re-rendered
texture           with new texture
to surface

Run script        Texture is 
that modifies     re-rendered
texture on        with script caused
that surface      changes

The user is free to apply the same original, unmodified texture similarly to other surfaces.

I would venture a guess that if you built and textured something in another program that didnt require you to pay L$10 per upload, it would look pretty much the same as it does in SL
Love your Taber place btw. I never see you there though.

Not overt harassment, no. (Though I'm sure some would disagree.) I want it because I don't like having to either ignore people or say "go away, I'm busy". It's not that I don't want to help you, or chat, or hang out, or come see something, or any of that. It's that I'm busy. Explaining this takes time and is irritating, and frequently recieved as being insulting.

I'd much prefer to simply appear to be offline. It would save a lot of hassle.

I'm thinking of just verbally abusing everyone I talk to indiscriminately.
Them: "Hey, Cat, how's it going? Can you take a look at a script I'm working on?"
Me: "Sure, I'd be glad to, you retard. I always like reading scripts written by complete morons."

Actually, this might work out better for everyone.

Heh. I'm actually starting to look around for good 3D texturing tools -- fitness inversely proportional to cost, nat ch.


Even though the semester is over, I don't have a lot of time for second life. Not only am I working, in a band, and (ha!) trying to finish my thesis, I've got a gal that's pretty demanding of my time on weekends.

But, I'll try to get on now and again. i'll just have to resist the urge to (re-)write that LLisp interpreter so that I can "finish" the Taber D'Ni structure.

Thanks for the compliment. Coming from you, that's especially meaningful!

jarod godel also wrote an lsl-based lisp interpreter his first couple of weeks inworld. what is with you godel people?

i endorse piprrr and hanks feature lists.

Interesting that we're both implementing LISP and have "Godel" last names. Coincidence, or not -- YOU decide on the next Geraldo!

In my case, I have an AI background. Moreover, I wanted a more powerful and interactive language that would allow me to easily create and manipulate objects from a command line. No more tweaking with the mouse -- just issue a few commands to get exactly the kind of objects and behavior you want.

LISP is a fairly simple and small language; LSL also crudely supports lists, so that's a third the battle. Unfortunately you cannot have lists of lists, nor will it be possible to directly create a "cons cell" where both of the list pointers refer to data items, and not to adjacent list members.

As the adage goes, though, most computer science problems can be solved by adding a layer of indirection. So I might be able to "fake" a properly linked list implementation by, um, implementing some form of virtual memory.

Needless to say, I've not gotten very far nor
have spent much time on this.



Thanks! I think that LSL is one of the weaker Second Life components. With a proper and potent scripting language, I can only imagine the elabore possibilities.

Cheers!