Confirmed users
954
edits
Firefox3.1/themes/visual navigation: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 17: | Line 17: | ||
I've been doing some sketches and thinking about what kinds of features related to previewing and searching content may make sense for the next version of Firefox. I've taken the sketches that I feel have the most potential and grouped them into three categories, based on how easy they might be to implement and how big a change they will cause. | I've been doing some sketches and thinking about what kinds of features related to previewing and searching content may make sense for the next version of Firefox. I've taken the sketches that I feel have the most potential and grouped them into three categories, based on how easy they might be to implement and how big a change they will cause. | ||
Evaluation for 3.1: | |||
* Canvas3d is available | |||
* Problems storing / retrieving image data quickly enough | |||
* Needs immediate consultation with the platform team | |||
* potentially low benefit (don't use coverflow, do use grid view) | |||
* Seems like rich ground, might need a bit more exploration | |||
* Smaller change & implementation (see below) may be appropriate for 3.1, while more major changes may need to wait until 4.0 | |||
* Many methods of visual navigation are already available as addons | |||
==Smaller Change & Implementation== | ==Smaller Change & Implementation== | ||
| Line 30: | Line 41: | ||
===Tab List in Sidebar=== | ===Tab List in Sidebar=== | ||
This isn't so much an idea for a design as much as a move to make the Firefox interface more | This isn't so much an idea for a design as much as a move to make the Firefox interface more intuitive. Currently history and bookmarks can be shown in the sidebar, but not tabs. | ||
http://people.mozilla.com/~jboriss/wiki/themes/list2.png | http://people.mozilla.com/~jboriss/wiki/themes/list2.png | ||
| Line 127: | Line 138: | ||
Another way to show content not as individual items but as steps in longer navigation tasks is by visually linking them. In these sketches, the navigation the user has taken is represented in a tree structure; whenever the user clicks a link, a branch is drawn from the location they were at to the one they are navigating to. This makes it easy to see the path the user has taken. | Another way to show content not as individual items but as steps in longer navigation tasks is by visually linking them. In these sketches, the navigation the user has taken is represented in a tree structure; whenever the user clicks a link, a branch is drawn from the location they were at to the one they are navigating to. This makes it easy to see the path the user has taken. | ||
===Time-Based View=== | |||
http://people.mozilla.com/~jboriss/wiki/themes/timed.png | |||
An issue with the current tab system is that many tabs can be opened, ignored, and forgotten about over time, silently eating up CPU in the background. With a timed interface, the user can see when they viewed which websites and perhaps delete unused websites accordingly. In the sketch, websites drift towards the left over time, so that new sites appear in the right-most column. | |||