Difference between revisions of "lure"

(Tutorials)
(Tutorials)
Line 12: Line 12:
 
== Tutorials ==
 
== Tutorials ==
  
* [[lure.tuts.parsepreview|Parser Preview]]
+
* [[lure.tuts.parsepreview |Parser Preview]]
* [[love2d.org/wiki/lure.tuts.xmlhttprequest|Using XMLHttpRequest]]
+
* [[lure.tuts.xmlhttprequest |Using XMLHttpRequest]]
  
 
== Documentation ==
 
== Documentation ==

Revision as of 09:20, 21 December 2011

Summary

LURE is an attempt to implement a hybrid xml/html DOM parser and renderer for the Love2d game engine. The goal of LURE is to provide the following:

  • A non-validating xml/html parser which generates a (somewhat) W3C Standards complaint DOM Object for use with love.
  • A html renderer which will display html markup in the love window.

Although we have a working prototype of the xml/html parser and DOM Object, we do not yet have a working renderer. Given the sheer size of the W3C DOM specification, this area will serve to document and track the current status of DOM Interface implementations.

Lure's purpose will NOT be to implement a web browser in Love2d, that is just ridiculous :D Instead, Lure's purpose will be to provide the core xml/html DOM interfaces allowing Lovers the ability to to work with xml/html data structures and to render basic html to the love window for simple UI.

Tutorials

  • [[lure.tuts.parsepreview |Parser Preview]]
  • [[lure.tuts.xmlhttprequest |Using XMLHttpRequest]]

Documentation

Lure Functions

Function Description Implemented
lure.load() Load function to handle loading xml/html data from various sources (ex: flatfile) Yes
lure.save() Saves a lure dom Object to flat file No
lure.update() Update function to handle dom updates & changes No
lure.draw() Draw function to render html to the lure window (if any html exists in the lure dom) No

Lure Objects

Object Description Implemented
Lure Window The Window object represents the Love window No
Lure History The history object contains past loaded xml/html documents No

Lure DOM Reference

Objects present in this table are DOM objects currently planned for implementation. Not all W3C DOM objects will be implemented.

Object Description Implemented
DOM Node The Node object represents a single node in the document tree Yes
DOM NodeList The NodeList object represents an ordered list of nodes Yes
DOM NamedNodeMap The NamedNodeMap object represents an unordered list of nodes. Yes
DOM document The Document object represents the entire XML/HTML document. Yes
DOM Element The Element object represents an element in an XML/HTML document Yes
DOM Attribute The Attr object represents an attribute of an Element object. Yes
DOM Text The Text object represents the textual content of an element or attribute. Yes
DOM CDATA The CDATASection object represents a CDATA section in a document. Yes
DOM Comment The Comment object represents the content of comment nodes in a document. Yes
DOM DOMParser DOMParser object parses xml/html text and returns a DOM Object Yes
DOM XMLHttpRequest XMLHttpRequest object can make synchronous or synchronous http requests to external web resources Yes
DOM HTMLEvent No
DOM HTMLAnchor No
DOM HTMLBody No
DOM HTMLButton No
DOM HTMLDiv No
DOM HTMLForm No
DOM HTMLImage No
DOM HTMLInput Button No
DOM HTMLInput Checkbox No
DOM HTMLInput Hidden No
DOM HTMLInput Password No
DOM HTMLInput Radio No
DOM HTMLInput Reset No
DOM HTMLInput Submit No
DOM HTMLInput Text No
DOM HTMLLink No
DOM HTMLOption No
DOM HTMLScript Represents an individual script element. asserts lua script directly from the document. Yes
DOM HTMLSelect No
DOM HTMLStyle The Style object represents an individual style element. Yes
DOM HTMLStylesheet Stylesheet object represents an individual stylesheet. Yes
DOM HTMLCssRule HTMLCssRule object represents an individual Css Rule. Yes
DOM HTMLTable No
DOM HTMLtd/th No
DOM HTMLtr No
DOM HTMLTextArea No

MORE TO COME!