Nautilus usability

Thank you for your bug report, the bug tracker is not a place where you dump a list of requests the way you are doing it there. You should check that those requests are not already registered and then open a different bug for each issue with details on the versions you are using and reason why you think the change is a good idea, you might also want to consider sending the bug to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

???????

What else is the 1000 paper cuts for then?
Is sounded like exactly the place to put these requests forward.

On Mon, Nov 30, 2009 at 7:35 PM, Sebastien Bacher <email address hidden> wrote:

> Thank you for your bug report, the bug tracker is not a place where you
> dump a list of requests the way you are doing it there. You should check
> that those requests are not already registered and then open a different
> bug for each issue with details on the versions you are using and reason
> why you think the change is a good idea, you might also want to consider
> sending the bug to the people writting the software
> (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)
>
> ** Changed in: nautilus (Ubuntu)
> Importance: Undecided => Wishlist
>
> ** Changed in: nautilus (Ubuntu)
> Status: New => Invalid
>
> ** Changed in: nautilus (Ubuntu)
> Assignee: (unassigned) => Ubuntu Desktop Bugs (desktop-bugs)
>
> --
> Nautilus usability
> https://bugs.launchpad.net/bugs/488129
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in One Hundred Paper Cuts: New
> Status in “nautilus” package in Ubuntu: Invalid
>
> Bug description:
> Some usability improvements needed:
>
> 1) Toolbar: button to switch on/off display of hidden files, button for
> network connections
> 2) Additional view mode: group by date, group by file type, group by size
> 3) When copying files and a overwrite warning is shown: show file size and
> date/time for both files
> 4) In File Save dialog: clearly indicate if the currently selected location
> can't be written to
> 5) File dialogs: allow switching of views like in full Nautilus view
> 6) File dialogs: button to toggle visibility of hidden files (currently
> inherits last setting, can't change)
> 7) File dialogs: allow network connect
> 8) File dialogs: allow mount
> 9) add a history feature
>

@Stephan

Try reading the response again ;) It's hard for developers to track big lists of problems like this. He's asking if you could file each request as a separate bug report. That'll make it easier for the developers to go about implementing these features/fixes.

Also, if you really want to speed up development, you should contact the Nautilus developers directly and present them with these problems. Unfortunately, the GNOME developers don't use launchpad for their bug tracking. So, the people working on the Papercuts project have to end up refiling a lot of these bugs "upstream" (where the GNOME developers are). This takes time and could mean that your bugs go unnoticed to these developers.

Ah...

That is *really* complicated for people who are not aware of all this. I had
the impression that the Papercuts was intended to get feedback from a
broader audience. For an *enduser* (even my wife is on Linux) the stated
problems are *one* issue. I understand, that for a developer they break down
into a large number of distinct programming tasks. So the big question would
be: reach out to the user population at large (eventually bugtrack isn't the
right way to collect this feedback and there must be a translation between
end user submissions and launchpad entries.
Lecturing end users about launch pad use is a good way to cut development
off from user feedback - which would be a pitty. Would be a bug in a
lauchpad: "Offer functionality to split one bug filed into a set of related
bugs" --- so the "master-bug" would close when all sub-bugs close.

So I have to submit again? Or is papercuts the wrong place? (I actually
wouldn't mind to sponsor one or the other bug since I lack the C skills to
fix them myself).

:-) stw

On Tue, Dec 1, 2009 at 11:03 PM, Daniel Fore <email address hidden>wrote:

> @Stephan
>
> Try reading the response again ;) It's hard for developers to track big
> lists of problems like this. He's asking if you could file each request
> as a separate bug report. That'll make it easier for the developers to
> go about implementing these features/fixes.
>
> Also, if you really want to speed up development, you should contact the
> Nautilus developers directly and present them with these problems.
> Unfortunately, the GNOME developers don't use launchpad for their bug
> tracking. So, the people working on the Papercuts project have to end up
> refiling a lot of these bugs "upstream" (where the GNOME developers
> are). This takes time and could mean that your bugs go unnoticed to
> these developers.
>
> --
> Nautilus usability
> https://bugs.launchpad.net/bugs/488129
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in One Hundred Paper Cuts: New
> Status in “nautilus” package in Ubuntu: Invalid
>
> Bug description:
> Some usability improvements needed:
>
> 1) Toolbar: button to switch on/off display of hidden files, button for
> network connections
> 2) Additional view mode: group by date, group by file type, group by size
> 3) When copying files and a overwrite warning is shown: show file size and
> date/time for both files
> 4) In File Save dialog: clearly indicate if the currently selected location
> can't be written to
> 5) File dialogs: allow switching of views like in full Nautilus view
> 6) File dialogs: button to toggle visibility of hidden files (currently
> inherits last setting, can't change)
> 7) File dialogs: allow network connect
> 8) File dialogs: allow mount
> 9) add a history feature
>

I know, it could be better. And that's a good idea about splitting up the bugs automatically! Maybe you should file that one against launchpad ;)

Yes, it would be nice if you submitted these again individually.

Papercuts isn't necessarily the *wrong* place to file these bugs. But, it would be helpful to file directly against Nautilus upstream to it's developers.