Written by descentspb the 3 May 08 at 13:18.

For example right-click on the partition and bring up it's options, where you can change the label.

For example right-click on the partition and bring up it's options, where you can change the label.

Written by vkadal the 7 May 13 at 10:41.

Kindly add an option "Rename" to the drop down menu when a drive is right clicked. This will facilitate to assign meaningful names to drives and easy to search for files

Kindly add an option "Rename" to the drop down menu when a drive is right clicked. This will facilitate to assign meaningful names to drives and easy to search for files

Written by choad the 10 Mar 09 at 15:12.

By default have the file browser view open in "My Files"



but have "home" right there in the path bar, so it's just one click away.

By default have the file browser view open in "My Files" <a href="http://img510.imageshack.us/img510/6537/28jkw4.png"><img src="http://img510.imageshack.us/img510/6537/28jkw4.th.png" /></a> but have "home" right there in the path bar, so it's just one click away.

Written by Psycho_zs the 10 Mar 09 at 18:59.

and leave ~/ for configs stuff

and leave ~/ for configs stuff

Written by aysiu the 10 Mar 09 at 19:57.

I don't see a problem here. My home directory doesn't look like that.

I don't see a problem here. My home directory doesn't look like that.

Written by Cé the 11 Mar 09 at 11:00.

The directory ~/Documents already exist in Ubuntu, so the only change needed is the link in the "Places" menubar, and the default place when the filebrowser start.

The directory ~/Documents already exist in Ubuntu, so the only change needed is the link in the "Places" menubar, and the default place when the filebrowser start.

Written by fmorel90 the 11 Mar 09 at 14:56.

Convince developers to put their application settings under ~./config so that the Home folder looks neater even when hidden files are shown.

Convince developers to put their application settings under ~./config so that the Home folder looks neater even when hidden files are shown.

Written by zeroangelmk1 the 28 Mar 09 at 18:20.

~/.hidden is a text file which is supposed to allow the file manager to prevent certain files and folders in the home from being viewed in normal mode (unless 'view hidden files' is enabled). Mentioning this in a tip dialogue or creating a link to a program which edits this file for the user would be useful.

~/.hidden is a text file which is supposed to allow the file manager to prevent certain files and folders in the home from being viewed in normal mode (unless 'view hidden files' is enabled). Mentioning this in a tip dialogue or creating a link to a program which edits this file for the user would be useful.

Written by cheesehead the 25 Mar 09 at 00:39.

Use Gconf for many config settings. That's what it's for, it's already included in the default install, and it offers many benefits to the apps that use it. Including KDE apps (Gconf does not require Gnome).
Many upstream projects could use volunteer love to help convert from .conf files to Gconf settings.

Use Gconf for many config settings. That's what it's for, it's already included in the default install, and it offers many benefits to the apps that use it. Including KDE apps (Gconf does not require Gnome). Many upstream projects could use volunteer love to help convert from .conf files to Gconf settings.

Written by benpicco the 26 Mar 09 at 03:12.

EDIT: So just use $XDG_CONFIG_HOME
http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html

By using an environment variable, everyone can decide where the config goes - one could even set $XDG_CONFIG_HOME=/tmp/ to try something out without overwriting the existing configuration - or having multiple configs for the same application with no effort. It's a flexible solution which would be even more easy to implement. (considering applications use getenv("HOME") to determine the home folder, the only change would be to replace getenv("HOME") with getenv("XDG_CONFIG_HOME").)

EDIT: So just use $XDG_CONFIG_HOME http://standards.freedesktop.org/basedir-spec/basedir-spec-0.6.html By using an environment variable, everyone can decide where the config goes - one could even set $XDG_CONFIG_HOME=/tmp/ to try something out without overwriting the existing configuration - or having multiple configs for the same application with no effort. It's a flexible solution which would be even more easy to implement. (considering applications use getenv("HOME") to determine the home folder, the only change would be to replace getenv("HOME") with getenv("XDG_CONFIG_HOME").)

Written by codexx the 1 Apr 09 at 06:08.

Either make the user folders or the autogenerated folders, have different icons.

This can be done in addition to other suggestions and i imagine be relatively simple

Either make the user folders or the autogenerated folders, have different icons. This can be done in addition to other suggestions and i imagine be relatively simple

Written by jamesisin the 7 Apr 09 at 06:26.

It certainly would help these matters if there was a simple button which would allow us to toggle hidden files on and off.

It certainly would help these matters if there was a simple button which would allow us to toggle hidden files on and off.

Written by tchalvakspam the 9 Apr 09 at 02:42.

Often app or config files and folders -can't- be moved, or renamed with a dot, or perhaps they will just be frequently auto-created even if they were moved. So we need to be able to just hide files or folders that we don't want to see ourselves, but still get used in that location by applications. Make that simple to do from the right click menu.

Often app or config files and folders -can't- be moved, or renamed with a dot, or perhaps they will just be frequently auto-created even if they were moved. So we need to be able to just hide files or folders that we don't want to see ourselves, but still get used in that location by applications. Make that simple to do from the right click menu.

Written by mykeus the 10 Oct 09 at 07:05.

I tend to edit configurations alot and one thing i did like about OSX was making use of Library Folder under each user home directory.

$HOME/.config are conforming to old standard and is it nasty.

$HOME/library not only can we eliminate the .dotfile orgy in each directory and better organize the home structure, but it would assist in user accessible files. ex. ruby gems, perl modules, skins, icons.

I tend to edit configurations alot and one thing i did like about OSX was making use of Library Folder under each user home directory. $HOME/.config are conforming to old standard and is it nasty. $HOME/library not only can we eliminate the .dotfile orgy in each directory and better organize the home structure, but it would assist in user accessible files. ex. ruby gems, perl modules, skins, icons.

Written by xeniac the 3 Oct 09 at 23:31.

Every graphical Application in Ubuntu should be conform to the Basedir Spec from the Free Desktop Project (See:
http://standards.freedesktop.org/basedir-spec/latest/index.html)

* User specific config files should be stored in gconf, or in $HOME/.config

* named pipes, cache-files, and any other application data should be saved under $HOME/.local/share/$APP_NAME

Every GUI application that does not conform to this spec, should be cousiderd faulty and a bug should be reported to fix it in upstream.

Pure CLI Packages should'nt be affected by this, to preserve UNIX compatibility.

Every graphical Application in Ubuntu should be conform to the Basedir Spec from the Free Desktop Project (See: http://standards.freedesktop.org/basedir-spec/latest/index.html) * User specific config files should be stored in gconf, or in $HOME/.config * named pipes, cache-files, and any other application data should be saved under $HOME/.local/share/$APP_NAME Every GUI application that does not conform to this spec, should be cousiderd faulty and a bug should be reported to fix it in upstream. Pure CLI Packages should'nt be affected by this, to preserve UNIX compatibility.

Written by Lachu the 29 Oct 09 at 18:30.

Prevent user from removing this files/directories. Each hidden file in user home directory should been protected from being removed by user. Nautilus, Dolphin, etc. should show warning messages in this situation.

Prevent user from removing this files/directories. Each hidden file in user home directory should been protected from being removed by user. Nautilus, Dolphin, etc. should show warning messages in this situation.

Written by geoff.m the 2 Nov 10 at 18:55.

When a folder doesn't have anything to expand it should not have a dropdown button, i.e. folders without subfolders in the folders panel on the left, and completely empty folders in the file panel on the right.

 

<p>When a folder doesn't have anything to expand it should not have a dropdown button, i.e. folders without subfolders in the folders panel on the left, and completely empty folders in the file panel on the right.</p><p>&nbsp;</p><p><img src="http://agora.ulaval.ca/~gemen16/nautilus_solution.jpg"></p>

Written by ak123 the 3 Nov 10 at 17:01.

If the folder is empty, Nautilus should attach an emblem to the icon to show the folder is empty. This can also be used when browsing in icon view and can also be applied to differentiate between folders with files and no subfolders and those that are completely empty.

If the folder is empty, Nautilus should attach an emblem to the icon to show the folder is empty. This can also be used when browsing in icon view and can also be applied to differentiate between folders with files and no subfolders and those that are completely empty.

Written by radioxid the 22 Apr 10 at 22:08.

Because the inconvenience is that the copy can break at any advanced or random time.

The best is to stop the copy at the beginning or at least to offer to avoid the files too large during the copy.

Because the inconvenience is that the copy can break at any advanced or random time. The best is to stop the copy at the beginning or at least to offer to avoid the files too large during the copy.

Written by Lachu the 24 Apr 10 at 07:42.

System should first try to reserve space for file, when may be copied to removable device. It will reduces IO operations and resolves this matter.

System should first try to reserve space for file, when may be copied to removable device. It will reduces IO operations and resolves this matter.

Written by rnerwein the 28 Apr 10 at 06:15.

if the warning will be implemented then there should also be
a posibilty to swicht this of by user account.

if the warning will be implemented then there should also be a posibilty to swicht this of by user account.

Written by thiagomoraesp the 28 Apr 10 at 14:01.

We need to explain to the user that this is a filesystem limitation and not a ubuntu limitation :)

We need to explain to the user that this is a filesystem limitation and not a ubuntu limitation :)

Written by gumshore the 28 Apr 10 at 23:23.

If the OS told the user that there is a limitation, thats fine, but chances are, the user still wants to copy the file. If we could display a dialog that offered to use file-roller or gzip or whatever to make an uncompressed archive of the file, and split it up, a user on a M$ computer could un-archive it with either WinR@R or 7-zip.

If the OS told the user that there is a limitation, thats fine, but chances are, the user still wants to copy the file. If we could display a dialog that offered to use file-roller or gzip or whatever to make an uncompressed archive of the file, and split it up, a user on a M$ computer could un-archive it with either WinR@R or 7-zip.

Written by robheus the 29 Apr 10 at 06:46.

The problem does not just show up when copying, since also when dowloading a file to a FAT file system, this could happen. Also, somewhat unrelated, on file systems which DO facilitate large files, the writing or copying of a file onto such a filesystem might break, because of a device (external USB harddisk) might be too slow.
Also a warning against that (having to wait an hour for a copy which still fails feels miserable) should be issued.

The solution would require two parts:
1. The tools that do such kind of copying (including file download) should warn against the breaking of the copy due to characteristics of the device and/or filesystem, and direct the user to utilize in that case another, better equipped tool.

2. Create a utility that can both split a file in (user definable, but with a good default value that depends on the filesystem in question) chunks/parts, and later join them together when doing the reverse transaction (for example: split with the option -j to join, and the option -s to split). As a command line option, offer also compression of the file to be written. Have the tool also resumable, so that it can resume a broken partial write, and/or have it check for the actual amount of the file written, and delay as necessary the copying if the device to write on is too slow to keep up.

3. Implement this also in other copy tools, like download managers, FTP, etc.

The problem does not just show up when copying, since also when dowloading a file to a FAT file system, this could happen. Also, somewhat unrelated, on file systems which DO facilitate large files, the writing or copying of a file onto such a filesystem might break, because of a device (external USB harddisk) might be too slow. Also a warning against that (having to wait an hour for a copy which still fails feels miserable) should be issued. The solution would require two parts: 1. The tools that do such kind of copying (including file download) should warn against the breaking of the copy due to characteristics of the device and/or filesystem, and direct the user to utilize in that case another, better equipped tool. 2. Create a utility that can both split a file in (user definable, but with a good default value that depends on the filesystem in question) chunks/parts, and later join them together when doing the reverse transaction (for example: split with the option -j to join, and the option -s <size> to split). As a command line option, offer also compression of the file to be written. Have the tool also resumable, so that it can resume a broken partial write, and/or have it check for the actual amount of the file written, and delay as necessary the copying if the device to write on is too slow to keep up. 3. Implement this also in other copy tools, like download managers, FTP, etc.

Written by DaVince the 14 May 10 at 22:57.

This means the Linux filesystem driver for FAT32 will handle the split files differently by showing, and reading, the split parts of the file as a single "normal" file.

Users of other OSes (like Windows) would see the split files instead.

This means the Linux filesystem driver for FAT32 will handle the split files differently by showing, and reading, the split parts of the file as a single "normal" file. Users of other OSes (like Windows) would see the split files instead.

Written by elypter the 27 May 10 at 18:51.

of cause with a warning and with an option to convert files.
Depending on the device a warning that most mp3players or cameras only work with fat

of cause with a warning and with an option to convert files. Depending on the device a warning that most mp3players or cameras only work with fat

Written by mitzampt the 14 Feb 11 at 13:20.

Offer as solution packing into smaller archives if the user only needs to store the file

Offer as solution packing into smaller archives if the user only needs to store the file

Written by Klau3 the 20 Apr 10 at 19:56.

The “Nautilus Further Actions Menu” shows different actions depending on the files you have selected or the way you have selected them. If you choose several pictures, you see the menu as shown in the mock-up.

THE MENU SHOULD ACT CONTENT AWARE!

To downsize the selected pictures you only have to right click on them -> 'Further Actions' -> 'Resize...'. A small window appears where you can select the most common settings. There you can set the overall size of all selected files after conversion (mockup upper corner right).

It is enough to click on the drop-down menu to alter the pre-determined final size of your file to fit it into a specific aspect ratio. The lower part of the window changes and you can select the settings you need – “Keep Aspect Ratio”, “Scale Unit” (percentages, centimeter, pixels, etc.).

It is important to keep options at a minimalistic level and to offer only options that are really necessary. Structure should also be clear and logical. Pre-settings are to be selected in such a way as to lead average users to their goals with a high certainty. The possible actions they can select from should make sense and take into account file type and combination of selected files.

<img src="http://nureineidee.files.wordpress.com/2010/04/nautilus-further-actions-menu.png" alt="Nautilus - Further Action Menu" /> The “Nautilus Further Actions Menu” shows different actions depending on the files you have selected or the way you have selected them. If you choose several pictures, you see the menu as shown in the mock-up. THE MENU SHOULD ACT CONTENT AWARE! To downsize the selected pictures you only have to right click on them -> 'Further Actions' -> 'Resize...'. A small window appears where you can select the most common settings. There you can set the overall size of all selected files after conversion (mockup upper corner right). It is enough to click on the drop-down menu to alter the pre-determined final size of your file to fit it into a specific aspect ratio. The lower part of the window changes and you can select the settings you need – “Keep Aspect Ratio”, “Scale Unit” (percentages, centimeter, pixels, etc.). It is important to keep options at a minimalistic level and to offer only options that are really necessary. Structure should also be clear and logical. Pre-settings are to be selected in such a way as to lead average users to their goals with a high certainty. The possible actions they can select from should make sense and take into account file type and combination of selected files. PDF: Merge, Split, Rotate, Convert to, Compress, Send to PIC: Convert to, Resize, Compress, Send to Office Format: Convert to, Compress, Send to

Written by Klau3 the 20 Apr 10 at 19:59.

This would make the right click menu clearer and easier to read – little used elements would not show straight away.

This would make the right click menu clearer and easier to read – little used elements would not show straight away.

Written by kp.stolk the 26 Apr 10 at 10:13.

Mabye we could just click 'copy' if we want to copy, if we want to 'copy to' there should be an sub menu right to the copy menu so you can click the submenu 'copy -> copy to'.

And the 'move to' should be right under the 'cut' menu, so we get: 'cut -> move to'.

this deletes 2 object from the submenu wich frees up some space and makes it more organised, and the 'Further Actions Menu' could be useful for the rest of the actions already proposed.(like convert, rezise etc.)

Afterall we have 1 less entry in the menu instead of 1 extra!

Mabye we could just click 'copy' if we want to copy, if we want to 'copy to' there should be an sub menu right to the copy menu so you can click the submenu 'copy -> copy to'. And the 'move to' should be right under the 'cut' menu, so we get: 'cut -> move to'. this deletes 2 object from the submenu wich frees up some space and makes it more organised, and the 'Further Actions Menu' could be useful for the rest of the actions already proposed.(like convert, rezise etc.) Afterall we have 1 less entry in the menu instead of 1 extra!

Written by ataide.carlos the 29 Apr 10 at 10:33.

Move all those options to a File Operations Menu.

If you just want to Copy/Move/Open then use the default Nautilus menu.
If the File selected is to be modifyied in any way, then you'd use this menu.

This would make the menu a bit "cleaner".

Move all those options to a File Operations Menu. If you just want to Copy/Move/Open then use the default Nautilus menu. If the File selected is to be modifyied in any way, then you'd use this menu. This would make the menu a bit "cleaner".

Written by lroder the 4 May 10 at 14:15.

I think this would be an excellent addition. For myself, I often find that I need to do a 'mass convert' of several photos taken from a hi-res camera to something more useable on a website. What's important to me is image resolution as well as size.

Windows XP had a Powertool called Image convert or something like that which let you change image resolution. It had a fair UI - not great, but functional. If you right clicked on an image or group of images, one of the options was 'resize pictures'. A handy tool.

I think this would be an excellent addition. For myself, I often find that I need to do a 'mass convert' of several photos taken from a hi-res camera to something more useable on a website. What's important to me is image resolution as well as size. Windows XP had a Powertool called Image convert or something like that which let you change image resolution. It had a fair UI - not great, but functional. If you right clicked on an image or group of images, one of the options was 'resize pictures'. A handy tool.

Written by chris_c the 12 May 10 at 06:56.

http://open.vitaminap.it/en/nautilus_pyextensions.htm

extending something like this (a simple python script) to your needs is not difficult and fun!

http://open.vitaminap.it/en/nautilus_pyextensions.htm extending something like this (a simple python script) to your needs is not difficult and fun!

Written by Penguin Guy the 16 May 10 at 16:19.

A lot of users never use half the features in the menu - allow the user to hide individual items.

A lot of users never use half the features in the menu - allow the user to hide individual items.