[sldev] New Scripting Functions

[Andre Roche]

Given that list my top 5 would be:

1.  Extensible Prim Attributes
2. llDetectedTouchFaceUV
3. llRequestAgentKey
4. llReturnObject
5. llGiveMoney
------------------------------

That is at least, if Extensible Prim Attributes is what I think it is,
it would be pretty high on a lot of priority lists here.  In case I'm
wrong though, could that item be clarified?

> On 9/27/07, Iridium Linden <iridium at lindenlab.com> wrote:
> >
> >
> > K, so here's the update on prioritizing those scripting functions we
> talked about at SL Views Six. (Click here for context if you don't know what
> I'm talking about or you've forgotten.)
> >
> > Angel Fluffy pointed out that in our prioritization of those script
> functions, we seemed to gravitate toward "low-hanging fruit." The reason for
> this is that these functions are easy-ish to implement and will have no
> adverse effect on performance. Additionally, these functions are actionable,
> meaning we can actually ship them in a reasonable amount of time. Some of
> the more ambitious suggestions thrown out in the scripting session were
> either technically difficult, posed some sort of community problem, or were
> altogether unmanageable (like llGiveInventory[List], how does this work for
> offline Residents? See Socialtext for the history).
> >
> > That said, here's a list of what seem to be the highest priority scripting
> functions requested:
> > 1. llDetectedTouchFaceUV - (Strife notes) I think the coords should be
> local to the texture UV. It wouldn't be limited to a range of 0,1. This
> would allow for some interesting interactions with llTextureAnim.
> > 2. llGiveMoney return value - Give the opportunity for the user to find
> out
> > 3. llReturnObject
> >
> > Other potential candidates were:
> > 4. llSetLinkPrimitiveParams with more link number control
> > 5. llDetectedTouchWorldPoint return global in world xyz coords
> > 6. llRequestAgentKey (blocking dataserver = error detection
> > 7. Extensible Prim Attributes (scratch area)
> > 8. llRegionParams or equivalent individual calls (with a PERMISSION_FOO
> permission?)
> > 9. llGetAvatarGroups
> > 10. llGetAvatarKeysOn[Parcel|Region]
> >
> > Before we slate these three functions as goals, I would like to obtain
> feedback from:
> > 1) You-SL Views group. If there is disagreement on privileging #s1-3
> scripting functions, then let's put our heads together now and decide on a
> top five instead of a top three. Once we decide on a top five, I'd like to
> solicit feedback from ...
> > 2) SLDevs (open source contributors). SLDevs represent yet another body of
> knowledge that we can draw from. So I say let's ping 'em! Given how
> knowledgeable this group is, I don't think there will be much disagreement.
> >
> > /Iridium
> >