669
edits
User:Broccauley/Fixing TabCandy: Difference between revisions
m
→So what exactly is wrong with "TabCandy"?
Broccauley (talk | contribs) |
Broccauley (talk | contribs) |
||
| Line 14: | Line 14: | ||
#Because "TabCandy" hides my pages from me, I am actually ''forced'' to go through "TabCandy" to see all my pages; I can't use the more obvious, powerful, ''exposed'', tried-and-tested and consistent methods that I have available to me both from my OS and from other more obvious areas of the Firefox UI that have existed since FF2. I have to click and open "TabCandy" to edit the "page sets" and can't really see or edit these well by just using the tab-strip itself. Once I start using "TabCandy" I am '''locked into "TabCandy"'s "walled garden"''' - I shouldn't be forced like this to use a separate tool to perform basic page/tab/window management.<br><br> | #Because "TabCandy" hides my pages from me, I am actually ''forced'' to go through "TabCandy" to see all my pages; I can't use the more obvious, powerful, ''exposed'', tried-and-tested and consistent methods that I have available to me both from my OS and from other more obvious areas of the Firefox UI that have existed since FF2. I have to click and open "TabCandy" to edit the "page sets" and can't really see or edit these well by just using the tab-strip itself. Once I start using "TabCandy" I am '''locked into "TabCandy"'s "walled garden"''' - I shouldn't be forced like this to use a separate tool to perform basic page/tab/window management.<br><br> | ||
#TabCandy forces upon the user '''unnecessary extra layers of hierarchy''' between them and the actual page content, adding additional '''confusion''' and '''slowing down''' the ability to access page content.<br><br> | #TabCandy forces upon the user '''unnecessary extra layers of hierarchy''' between them and the actual page content, adding additional '''confusion''' and '''slowing down''' the ability to access page content.<br><br> | ||
#"TabCandy" only works on a '''per-window basis''', rather than showing me the bigger picture of ''all'' the web-browsing that I am actually doing. I can't count the number of times that I've had 3 or so windows open and then lose one of these "ghost" tabs into TabCandy's "Land of Limbo" and then have to dig through all the windows to try and find it again (making me actually LESS productive with "TabCandy" than without). This just '''discourages the existing good practice of partitioning your open tabbed pages into windows'''.<br><br>It seems as if "TabCandy" is trying to solve a problem that doesn't exist - i.e. making out that it's somehow a problem to have more than one window open at once -- this is not the case with a modern OS such as Windows 7, KDE | #"TabCandy" only works on a '''per-window basis''', rather than showing me the bigger picture of ''all'' the web-browsing that I am actually doing. I can't count the number of times that I've had 3 or so windows open and then lose one of these "ghost" tabs into TabCandy's "Land of Limbo" and then have to dig through all the windows to try and find it again (making me actually LESS productive with "TabCandy" than without). This just '''discourages the existing good practice of partitioning your open tabbed pages into windows'''.<br><br>It seems as if "TabCandy" is trying to solve a problem that doesn't exist - i.e. making out that it's somehow a problem to have more than one window open at once -- this is not the case with a modern OS such as Windows 7, KDE 4.5, or Snow Leopard -- therefore there is no reason to hide such windows. "TabCandy" actually makes it ''more difficult'' to work with several windows than before.<br><br>"TabCandy" is therefore taking the tried, tested, more flexible, powerful, and much more simple method of grouping tabbed pages by window, and completely throwing it "out the window" (if you excuse the recursive pun! :)). In summary, '''"Tab sets" != open windows'''.<br><br> | ||
#"TabCandy" doesn't really acknowledge or exploit the UI advantages and APIs that are now available in '''Windows 7'''. It also doesn't acknowledge that having '''5 or 6 different Firefox windows on Windows 7 is really not a problem for the user''' to deal with, especially if the new APIs are exploited to their full potential.<br><br> | #"TabCandy" doesn't really acknowledge or exploit the UI advantages and APIs that are now available in '''Windows 7'''. It also doesn't acknowledge that having '''5 or 6 different Firefox windows on Windows 7 is really not a problem for the user''' to deal with, especially if the new APIs are exploited to their full potential.<br><br> | ||
#"TabCandy" (and modern web-browsers in general) doesn't really acknowledge the fact that users shouldn't actually care about small inflexible UI elements for showing fixed-sized pages called "tabs". The user should care only about the web '''CONTENT '''or '''"pages"''' that they are browsing. <s>The new name of "Tab Sets" (whilst better than "Tab Candy") misguidedly still '''focuses its name on a small inflexible UI control called a "tab"'''.</s> ''(Edit: This has now been fixed with the excellent new name of "Panorama", however, the Firefox-UI and TabCandy/Panorama instruction video still over-use the word "tab".)<br><br> | #"TabCandy" (and modern web-browsers in general) doesn't really acknowledge the fact that users shouldn't actually care about small inflexible UI elements for showing fixed-sized pages called "tabs". The user should care only about the web '''CONTENT '''or '''"pages"''' that they are browsing. <s>The new name of "Tab Sets" (whilst better than "Tab Candy") misguidedly still '''focuses its name on a small inflexible UI control called a "tab"'''.</s> ''(Edit: This has now been fixed with the excellent new name of "Panorama", however, the Firefox-UI and TabCandy/Panorama instruction video still over-use the word "tab".)<br><br> | ||