User:David Regev/Ubiquitous Firefox: Difference between revisions

User:David Regev/Ubiquitous Firefox (view source)

9 bytes added , 24 January 2011

m

Confirmed users

187

edits

@@ Line 152: / Line 152: @@
 [[Image:Ubiquitous Firefox – Figure 7.png|thumb|center|256px|Figure 7: Solving the ‘Too Many Tabs’ Problem ([http://www.flickr.com/photos/davidregev/5341947391/ annotated version])]]
-When one traverses one of these tab trees, there is usually a predictable and liner order in which the page at each node is read. This is the depth-fist order (which is arguably more efficient than a breadth-first order). Such a flow was boosted by Firefox 3.6 when spawned tabs were made to appear adjacent to their parent and in order. What if we simply collapsed the tree into a single dimension, preserving its natural reading order? This is what the diagram shows.
+When one traverses one of these tab trees, there is usually a predictable and liner order in which the page at each node is read. This is the depth-first order (which is arguably more efficient than a breadth-first order). Such a flow was boosted by Firefox 3.6 when spawned tabs were made to appear adjacent to their parent and in order. What if we simply collapsed the tree into a single dimension, preserving its natural reading order? This is exactly what the diagram shows.
 So, how does it work? These are the rest of its features: