> Right. The question I have is, if we were to increase the > navigational features of Shotwell, should we follow a file manager > model or a web browser model (or, like Nautilus, offer a hybrid)?
I guess that the mere fact that there is a sidebar that allows jumping to any position makes it a hybrid model as it is not purely linear. Add to that a "Go back" button that goes back to the previous view (in most cases, that means the "parent" view) and you get the best of both worlds? > That's possible, but I have to wonder if people are really that > confused by this (and need a button). For example, Nautilus doesn't > have a "launch" or "open" button, but people understand to > double-click to open a program or a document. Except that Nautilus allows using it in single-click mode (this is how I have set it up for every non-computer-savy user whose computer I maintain; this is even how I use it, myself) > This was a conscious decision on our part. We realize it violates HIG > but went with it anyway for one of the reasons you mentioned: the > human gaze moves upward. As a photo app, we felt people are more > interested in seeing their photos than our toolbar and wanted to put > them up higher. I know I'm biased, but I actually feel this when I > use other photo/image apps -- I feel like the toolbar is crowding out > the photos, which are the things I'm more interested in. Hm, quite an interesting perspective. But then, aren't you similarly annoyed by other content-centric apps that have toolbars on top (like office suites, tomboy/gnote, inkscape, audio editors, etc.? It's kind of a tradition across the desktop, so you need solid reasons to break consistency, I guess. My 2ยข. _______________________________________________ Shotwell mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/shotwell
