HTML Interfaces I'm plotting an alternate main screen rendering of bookmarks in Mozilla. It's essentially yahoo/dmoz style and has three key attributes. A breadcrumb stating the current place in the hierarchy, a search box, and a listing of current descendants with the top X grandchildren nested under the children.UPDATE: mozHoo project homepage
Tech Trail
jslib seems to only read RDF from files
This n.p.m post shows how you'd traverse the bookmarks in 2000. Looks updateable
As Zoe and it's recent buzz has shown, there are times when an HTML interface is best. It's remarkable to me the number of software development teams that do not realize that for certain things, humans have never been better computer users than they are now with the web. (of course, there are teams that are biased torward web apps, ignoring the potential of dedicated UIs too).
Once I get the bookmark view done, I'm eager to have a way to preview titles of recently arrived email messages from whatever browser window I happen to be on (or get to first).
So why did Netscape go with XUL in the re-beginning? (XUL is Mozilla's cross platform UI toolkit)
Some very interesting tidbits:
- ability to place HTML inside widgets like the trees and toolbars"
- HTML is designed to handle documents and not to handle applications. It makes sense to maintain a clean separation between the Web APPLICATION and the Web DOCUMENTS that the application contains. By keeping the DOM tree in a sandbox (safely insulated from the containing AOM tree in which it might occur), you have an easy means of distinguishing the two trees and preventing scripts in the DOM tree from manipulating the AOM tree
- Alas, the document is unfinshed...
6:24:50 PM 
|
