342
edits
mNo edit summary |
|||
Line 10: | Line 10: | ||
====Results==== | ====Results==== | ||
*there is a clear separation of frequently used pages and the “treasure trove” the habits of the user decide if they are stored in files with a command structure or not | *there is a clear separation of frequently used pages and the “treasure trove”: the habits of the user decide if they are stored in files with a command structure or not | ||
*frequently used pages are seldom expanded and liable to a static hierarchy, therefore they have a fixed position and an easily recognizable icon | *frequently used pages are seldom expanded and liable to a static hierarchy, therefore they have a fixed position and an easily recognizable icon | ||
*the bookmarks in the treasure trove are sometimes renamed to fit the user, but mostly not bothered with | *the bookmarks in the treasure trove are sometimes renamed to fit the user, but mostly not bothered with | ||
*users which are very familiar with the existing bookmarks system are unsure of and even fear the changes the system could undergo, because their usual system of recognition and memorization of bookmarks could become unsuitable | *users which are very familiar with the existing bookmarks system are unsure of and even fear the changes the system could undergo, because their usual system of recognition and memorization of bookmarks could become unsuitable | ||
*bookmarks are mostly only edited if they’re used frequently, otherwise it’s not worth the bother | *bookmarks are mostly only edited if they’re used frequently, otherwise it’s not worth the bother | ||
*easy synchronization between different devices should be possible as some users tend to use their bookmarks on more than one device the new visual implementation should be able to be viewed with different resolutions | *easy synchronization between different devices should be possible as some users tend to use their bookmarks on more than one device: the new visual implementation should be able to be viewed with different resolutions | ||
*the user wants to categorize and file their bookmarks fast and without much effort | *the user wants to categorize and file their bookmarks fast and without much effort | ||
*it’s important that they don’t have to dedicate much time to create a bookmark and everything stays cleanly arranged | *it’s important that they don’t have to dedicate much time to create a bookmark and everything stays cleanly arranged | ||
====Goals==== | ====Goals==== | ||
*making the | *making the bookmark system more attractive by means of a visual wall-like display | ||
*users that are familiar with the existing system should still be able to use the modified version without the loss of their structure or a loss of quality | *users that are familiar with the existing system should still be able to use the modified version without the loss of their structure or a loss of quality | ||
*frequently used webpages | *the user should be able to visit frequently used webpages without detours and less important pages should be found more easily | ||
*users should be able to quickly retrieve their bookmarks (with the use of logical search criteria) | *users should be able to quickly retrieve their bookmarks (with the use of logical search criteria) | ||
*the file system should be retained so the user doesn’t have to adjust to a too new system | *the file system should be retained so the user doesn’t have to adjust to a too new system |
edits