Bookmarks Design Discussion: Difference between revisions

m (Reverted edit of Yeik, changed back to last version by RyanJones)
 
Line 50: Line 50:


The graphical interfaces for bookmarks must address two different purposes. One is quick access to websites and the other one is managing a personal index. Both concepts have been kept in one interface so far but it would be better to have two tailored interfaces: one for fast access to frequently visited websites following the design principles of program menus or sidebars with a small number of items, and the other one for managing and searching the personal WEB INDEX ("permanent history") of marked and tagged websites.  
The graphical interfaces for bookmarks must address two different purposes. One is quick access to websites and the other one is managing a personal index. Both concepts have been kept in one interface so far but it would be better to have two tailored interfaces: one for fast access to frequently visited websites following the design principles of program menus or sidebars with a small number of items, and the other one for managing and searching the personal WEB INDEX ("permanent history") of marked and tagged websites.  
For more details please see: http://tdot.blog-city.com/rethinking_bookmarks_ui.htm
For more details please see: http://pubnotes.wordpress.com/2007/10/14/rethinking-bookmarks-ui/


=== Interaction With Other Bookmark Providers ===
=== Interaction With Other Bookmark Providers ===


Bookmark providers that provide items will be subject to the same labelling mechanism.  However, bookmarks that provide containers will be a special case, since they will live a dual item/container life.  RSS bookmarks in particular will, .....
Bookmark providers that provide items will be subject to the same labelling mechanism.  However, bookmarks that provide containers will be a special case, since they will live a dual item/container life.  RSS bookmarks in particular will, .....
45

edits