Difference between revisions of "lure"
(→Lure DOM Reference) |
(→Lure DOM Reference) |
||
Line 171: | Line 171: | ||
|- | |- | ||
| [[lure.dom.style|DOM style]] | | [[lure.dom.style|DOM style]] | ||
− | |style="padding-left:10px;"| | + | |style="padding-left:10px;"|The Style object represents an individual style statement. |
|style="padding-left:10px;"|Yes | |style="padding-left:10px;"|Yes | ||
|- | |- |
Revision as of 08:20, 6 November 2011
Contents
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
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 | 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 Events | No | |
DOM Anchor | No | |
DOM Body | No | |
DOM Button | No | |
DOM Form | No | |
DOM Image | No | |
DOM Input Button | No | |
DOM Input Checkbox | No | |
DOM Input Hidden | No | |
DOM Input Password | No | |
DOM Input Radio | No | |
DOM Input Reset | No | |
DOM Input Submit | No | |
DOM Input Text | No | |
DOM Link | No | |
DOM Option | No | |
DOM Select | No | |
DOM style | The Style object represents an individual style statement. | Yes |
DOM Table | No | |
DOM td/th | No | |
DOM tr | No | |
DOM TextArea | No |
MORE TO COME!