GNOME Bugzilla – Bug 670572
Save-As dialog box is not consistent with Nautilus' SidePane layout
Last modified: 2012-08-02 12:30:44 UTC
Created attachment 208172 [details] Nautilus SidePane I spend a lot of time "teaching" people how to use Ubuntu. A lot of the people I teach are not very computer savvy. It is confusing to people when they see in the Nautilus SidePane how things are categorized by DEVICES, COMPUTER, NETWORK only to be confronted with a lack of the same categorization/demarcation when they are presented with a Save-As dialog box. This results in users not fully understanding where something is going to be saved. The Save-As dialog box should use the same categorization/demarcation paradigm as the Nautilus SidePane. For example, look at the two screenshots I have attached. In the "Nautilus SidePane" screenshot, you can see that HOME, DESKTOP, and FILE SYSTEM are all located under the COMPUTER heading. This clearly communicates that these folders are located on the user's computer. Now look at the "Save-As dialog SidePane". Notice how the USER, DESKTOP, and FILE SYSTEM folders are located where the DEVICES are listed? This is confusing. These folders are located on the COMPUTER and yet they are being listed along with DEVICES. The Save-As dialog box layout should match Nautilus' SidePane layout. That is, USER, DESKTOP, and FILE SYSTEM should be moved below the "DEVICES section" so they are listed together with the other folders located on the user's computer.
Created attachment 208173 [details] Save-As dialog SidePane
This looks like a valid issue. I don't see a reason why these two should be different, and it makes sense to be consistent.
Ah, this old chestnut :) The "Places" inconsistency was a regular bugbear of mine in GNOME 2.x, too: http://blogs.gnome.org/calum/2006/04/10/all-over-the-places/ http://blogs.gnome.org/calum/2009/01/12/different-day-same-places/
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 650363 ***