Confirmed users
146
edits
DOM/XPath Generator: Difference between revisions
Jump to navigation
Jump to search
m
→Potential Use Cases
| Line 34: | Line 34: | ||
http://annozilla.mozdev.org/ | http://annozilla.mozdev.org/ | ||
"My annozilla extension is a client for the W3C's Annotea server, which uses XPointers. I guess that XPointer generation/resolution would be easier with build-in XPath support." -- Matthew Wilson | "My annozilla extension is a client for the W3C's Annotea server, which uses XPointers. I guess that XPointer generation/resolution would be easier with build-in XPath support." -- Matthew Wilson | ||
(From the implementation bug) | |||
"This kind of thing would be useful for | |||
http://www.melez.com/mykzilla/2006/01/son-of-live-bookmarks.html, too. | |||
(Oops, ok, pornzilla, too.) | |||
Both of which only make sense if we serialize both the expression and the | |||
namespace resolver (assuming that we need to handle XML to be future proof)." -- Alex Hecht | |||
[http://verbosio.mozdev.org Verbosio] would be able to translate a XPath for a document it's editing into a XPath for a XUL tree (a la DOM Inspector) representing the document's structure. This would be through simple text replaces. Thus, a node found in the master document would easily translate to a XUL tree item. | [http://verbosio.mozdev.org Verbosio] would be able to translate a XPath for a document it's editing into a XPath for a XUL tree (a la DOM Inspector) representing the document's structure. This would be through simple text replaces. Thus, a node found in the master document would easily translate to a XUL tree item. | ||