Difference between revisions of "Talk:Extensible Prim Attributes from LSL"
Gigs Taggart (talk | contribs) m (Talk:LSL To Client Comms moved to Talk:Extensible Prim Attributes from LSL: Clearer name.) |
|||
| (3 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
This would be useful. In the interim, is the object description usable for holding meta data? This may still be sent to the client even if it's not normally visible on objects you don't own. This is the case with object names, at least. It's worth investigation. --[[User:Soft Noel|Soft Noel]] 13:30, 24 February 2007 (PST) | This would be useful. In the interim, is the object description usable for holding meta data? This may still be sent to the client even if it's not normally visible on objects you don't own. This is the case with object names, at least. It's worth investigation. --[[User:Soft Noel|Soft Noel]] 13:30, 24 February 2007 (PST) | ||
This would be quite useful for my raytracer work. Right now, I'm thinking of re-using the lighting parameters to carry advanced material properties: light radius can also store index of refraction, light intensity can be used for specular highlight intensity, and light falloff can store specular highlight size. --[[User:Carnildo Greenacre|Carnildo Greenacre]] 20:55, 25 February 2007 (PST) | |||
There are an awful lot of places other than open source where this kind of thing is necessary. | |||
Objects really need the same kind of name-value attribute list they have in MUDs and MUCKs. -- [[User:Argent Stonecutter|Argent Stonecutter]] 14:28, 26 June 2007 (PDT) | |||
It seems to me that all that is needed is some mechanism that allows a script to "say" an arbitrary string that the client will see. Why not just use one of the ll*Say() commands. Pick a channel unlikely to be used for anything else and then make the message following some sort of protocol. Modify the client code to intercept these and do the appropriate action. No need to change anything on the server side. Later, once it is all worked out, perhaps then you can see about getting it added to LSL. -- [[User:Kubota Homewood|Kubota Homewood]] 18:16, 24 September 2007 (PDT) | |||
Chat on channels other than 0 aren't sent to the client. In addition, chat is somewhat heavyweight for cases like the one [[User:Carnildo Greenacre|Carnildo Greenacre]] mentioned, since there may easily be hundreds of prims in draw distance that need to pass extra graphical attributes their index of refraction to the client. [[User:Argent Stonecutter|Argent Stonecutter]] 14:42, 31 December 2007 (PST) | |||
Latest revision as of 14:42, 31 December 2007
This would be useful. In the interim, is the object description usable for holding meta data? This may still be sent to the client even if it's not normally visible on objects you don't own. This is the case with object names, at least. It's worth investigation. --Soft Noel 13:30, 24 February 2007 (PST)
This would be quite useful for my raytracer work. Right now, I'm thinking of re-using the lighting parameters to carry advanced material properties: light radius can also store index of refraction, light intensity can be used for specular highlight intensity, and light falloff can store specular highlight size. --Carnildo Greenacre 20:55, 25 February 2007 (PST)
There are an awful lot of places other than open source where this kind of thing is necessary.
Objects really need the same kind of name-value attribute list they have in MUDs and MUCKs. -- Argent Stonecutter 14:28, 26 June 2007 (PDT)
It seems to me that all that is needed is some mechanism that allows a script to "say" an arbitrary string that the client will see. Why not just use one of the ll*Say() commands. Pick a channel unlikely to be used for anything else and then make the message following some sort of protocol. Modify the client code to intercept these and do the appropriate action. No need to change anything on the server side. Later, once it is all worked out, perhaps then you can see about getting it added to LSL. -- Kubota Homewood 18:16, 24 September 2007 (PDT)
Chat on channels other than 0 aren't sent to the client. In addition, chat is somewhat heavyweight for cases like the one Carnildo Greenacre mentioned, since there may easily be hundreds of prims in draw distance that need to pass extra graphical attributes their index of refraction to the client. Argent Stonecutter 14:42, 31 December 2007 (PST)