Difference between revisions of "Talk:Programmatic Textures"
Gigs Taggart (talk | contribs) (questioning renderhtml and stringasset) |
|||
| Line 1: | Line 1: | ||
Changed the parameters to llRenderText to match the other call. -- [[User:Argent Stonecutter|Argent Stonecutter]] 12:05, 26 January 2007 (PST) | Changed the parameters to llRenderText to match the other call. -- [[User:Argent Stonecutter|Argent Stonecutter]] 12:05, 26 January 2007 (PST) | ||
==RenderHTML== | |||
What problem does renderHTML solve? I don't see much use in a static, nonrefreshable texture that just happens to be defined in HTML. Remember we are going after a different problem domain than what can be accomplished with static texture uploads that we have now. This isn't merely a "different way to get stuff on a prim", we want a system where textures can be dynamic in response to the LSL running in the object. | |||
The string2asset proposal has the same problem. The point of this isn't to make static images that will be used over and over, it's to generate things on the fly that are temporary in nature (such as a textual output or a status display). | |||
I'm going to remove these two proposals, as they are orthogonal to what this proposal is trying to accomplish. If you want to make them into their own feature requests, feel free. I'm going to move their text here for easy access. [[User:Gigs Taggart|Gigs Taggart]] 05:59, 13 February 2007 (PST) | |||
Revision as of 05:59, 13 February 2007
Changed the parameters to llRenderText to match the other call. -- Argent Stonecutter 12:05, 26 January 2007 (PST)
RenderHTML
What problem does renderHTML solve? I don't see much use in a static, nonrefreshable texture that just happens to be defined in HTML. Remember we are going after a different problem domain than what can be accomplished with static texture uploads that we have now. This isn't merely a "different way to get stuff on a prim", we want a system where textures can be dynamic in response to the LSL running in the object.
The string2asset proposal has the same problem. The point of this isn't to make static images that will be used over and over, it's to generate things on the fly that are temporary in nature (such as a textual output or a status display).
I'm going to remove these two proposals, as they are orthogonal to what this proposal is trying to accomplish. If you want to make them into their own feature requests, feel free. I'm going to move their text here for easy access. Gigs Taggart 05:59, 13 February 2007 (PST)