Difference between revisions of "HTML on a Prim Taxonomy"

From Second Life Wiki
Jump to navigation Jump to search
 
(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 11: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

  1. Images
    • Images should be referenced by UUID
    • Images must be full permission unless contained in the prim?

Uses

  1. Books
  2. Magazines
  3. Catalog
  4. Help Manual
  5. Advertisements

HTML from scripting

HTML is rendered from the output of a script.

Issues

  1. Script Memory Constraints
  2. Images
    • Images should be referenced by UUID
    • Images must be full permission unless contained in the prim??

Uses

  1. HUDs (with images)
  2. Changing Text Displays
  3. Item Vendors
  4. 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

  1. Plugins that can't be rendered
  2. Referenced images can't be by UUID, must be on the webpage ??
  3. Can't be directly tied into scripts ??

Solutions to Issues

  1. A URI, secondlifeasset:// , could be used to reference assets by UUID

Uses

  1. Web Browsing
  2. Books/comics
    1. Text on a prim
    2. PDF-like manuals
    3. Comic strips
  3. Magazines
  4. Shopping
    1. Vending machines
    2. Shopping carts
    3. Interface with eBay/Paypal and buy real items in-world
  5. Advertisements
  6. HUD Elements
  7. Gui Screens
  8. Text Displays
  9. Images on a prim
    1. Web-based textures
    2. Share Flickr and Imagebucket photos
    3. Comic strips
  10. Better interfaces for in-world systems
    1. Better in-world computers
    2. Movie screens
  11. Better means of in-to-out world chatting:
    1. Can use IRC-CGI program
      1. The Chatzilla extension for Firefox could be modified to run under uBrowser
    2. Can follow Twitter feeds
    3. Can use web-based AIM, IRC, etc.

In-Client Blowser

Issues

  1. Only displays help page in default client.
  2. Will not render some pages properly (Flash?).

Solutions to Issues

  1. Either:
    1. Add an address bar, or
    2. Implement llLaunchBrowser command in LSL.
  2. Tell people to only use AJAX.

Uses

  1. See: World Wide Web (http://en.wikipedia.org/wiki/World_Wide_Web)
  2. 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