Hi, On Thu, Aug 2, 2012 at 8:40 AM, Ben Gamari <bgamari.f...@gmail.com> wrote:
> > To be clear, for my use-case it is important to understand that files > not matching my criteria should not be hidden from view (as is usual > in search). I simply want a want to efficiently move around the view, > all files included. For instance, if I want to take a look at my 100nM > dataset, I want to be able to quickly move to "100nM.dat" and still > easily see the neighboring "150nM.dat", "200nM.dat", and "250nM.dat" > files. > > This is why I say that my "browsing" usecase differs substantially from > "search". While in "search" the user wants to isolate a group of files, in > "browsing" you simply seek to locate a group of files in a region of the > filename space. > > At the UX Hackfest we were discussing this type of usecase in relation to the file chooser [1]. Having filters in the file chooser may not satisfy your use case, but I wanted to let you know that such uses are being discussed. There was also a lengthy discussion about improving search, as Jon mentioned in his blog post [2]. I think that you will see improvements in this area in the near future. Thanks for your feedback and engagement, Meg Ford [1] https://github.com/gnome-design-team/gnome-mockups/blob/master/file%20chooser/ux-hackfest1-noheader.svg [2] http://blogs.gnome.org/mccann/ Cheers, > > - Ben > > > -- > nautilus-list mailing list > nautilus-list@gnome.org > https://mail.gnome.org/mailman/listinfo/nautilus-list >
-- nautilus-list mailing list nautilus-list@gnome.org https://mail.gnome.org/mailman/listinfo/nautilus-list
