01-25-2006 22:53
I have been reading the specs on the Linden Scripting Language and viewing some of the samples and library posts.. Why is everything so raw? I find it more effective to use an object oriented style of scripting, for instance; instead of:


CODE

llRequestPermissions(llGetOwner(), PERMISSION_TRIGGER_ANIMATION);
llStartAnimation("sit");


It makes more sense to:
CODE

integer SitError = LLAPI.GetOwner.StartAnimation(LLAPI.Animations.Sit);
if (SitError > 0)
{
//tossError
}

More control available that way.
from what I am reading I cant use the use the familiar syntax of a c/Java style language 'this' as in:

CODE

void LLAPI()
{
this.GetOwner = GetOwner(); // get my owner object/function.
this.GetTime = llGetTime(); // easy association
}



So I must create “instances of geometry” for each object just to simplify coding?
Why is this not thought out from the start? I was taught that standard application architecture is to design front to back. Not middle meat and the backend then add the API.