Difference between revisions of "HTML on a Prim Taxonomy"
Zero Linden (talk | contribs) |
Gigs Taggart (talk | contribs) (web textures mention) |
||
Line 93: | Line 93: | ||
# See: World Wide Web (http://en.wikipedia.org/wiki/World_Wide_Web) | # See: World Wide Web (http://en.wikipedia.org/wiki/World_Wide_Web) | ||
# See: HTML on a Prim | # See: HTML on a Prim | ||
== HTTP Fetched Textures == | |||
Instead of full HTML on a prim, one option is client-side http fetched textures. This solves like 85% of the use-cases that HTML on a prim solves, with a lot less effort required. | |||
[[Web Textures]] |
Revision as of 12:31, 21 March 2007
This page is to help us enumerate the different possibilities and options for "HTML on a Prim". It is here so that we are all talking the same thing, and know what we all mean by the different options.
See also: HTML on a Prim Use Cases
HTML on a Prim can come from several possible sources. Each one having a distinct use, where some overlap may occur between classes of use.
HTML from a Notecard
HTML is rendered from a notecard contained within the prim, or a UUID reference to the notecard.
Issues
- Images
- Images should be referenced by UUID
- Images must be full permission unless contained in the prim?
Uses
- Books
- Magazines
- Catalog
- Help Manual
- Advertisements
HTML from scripting
HTML is rendered from the output of a script.
Issues
- Script Memory Constraints
- Images
- Images should be referenced by UUID
- Images must be full permission unless contained in the prim??
Uses
- HUDs (with images)
- Changing Text Displays
- Item Vendors
- GUI Screens
This method could be combined with HTML from a notecard for forms. Would require new script events to handle form submission
HTML from the internet
HTML is rendered from an internet site
Issues
- Plugins that can't be rendered
- Referenced images can't be by UUID, must be on the webpage ??
- Can't be directly tied into scripts ??
Solutions to Issues
- A URI, secondlifeasset:// , could be used to reference assets by UUID
Uses
- Web Browsing
- Books/comics
- Text on a prim
- PDF-like manuals
- Comic strips
- Magazines
- Shopping
- Vending machines
- Shopping carts
- Interface with eBay/Paypal and buy real items in-world
- Advertisements
- HUD Elements
- Gui Screens
- Text Displays
- Images on a prim
- Web-based textures
- Share Flickr and Imagebucket photos
- Comic strips
- Better interfaces for in-world systems
- Better in-world computers
- Movie screens
- Better means of in-to-out world chatting:
- Can use IRC-CGI program
- The Chatzilla extension for Firefox could be modified to run under uBrowser
- Can follow Twitter feeds
- Can use web-based AIM, IRC, etc.
- Can use IRC-CGI program
In-Client Blowser
Issues
- Only displays help page in default client.
- Will not render some pages properly (Flash?).
Solutions to Issues
- Either:
- Add an address bar, or
- Implement llLaunchBrowser command in LSL.
- Tell people to only use AJAX.
Uses
- See: World Wide Web (http://en.wikipedia.org/wiki/World_Wide_Web)
- See: HTML on a Prim
HTTP Fetched Textures
Instead of full HTML on a prim, one option is client-side http fetched textures. This solves like 85% of the use-cases that HTML on a prim solves, with a lot less effort required.