Written by Penguin Guy the 29 Mar 10 at 21:02.

A checkbox grid editor is both easier to understand and more widely used. Enable Nautilus' advanced permissions editor by default.

A checkbox grid editor is both easier to understand and <a href="http://images.google.com/images?q=file+permissions">more widely used</a>. Enable Nautilus' advanced permissions editor by default. <img src="http://dl.dropbox.com/u/1217030/Ubuntu%20Brainstorm/New%20Permissions.png" />

Written by Ssdg the 30 Mar 10 at 09:46.

As you can see on #1 the interface uses words like: "set user ID"

It's a bit complex for low level users. We need them to get as quickly as possible what a checkbox means. For exemple:

Set user ID will become : "the program will have same rights as the owner has(set user ID)"

As you can see on #1 the interface uses words like: "set user ID" It's a bit complex for low level users. We need them to get as quickly as possible what a checkbox means. For exemple: Set user ID will become : "the program will have same rights as the owner has(set user ID)"

Written by la_serpe the 31 Mar 10 at 09:29.

It's impossible to change some options in this menu, unless you are root. There is no way to become root through GUI. This should change.

It's impossible to change some options in this menu, unless you are root. There is no way to become root through GUI. This should change.

Written by m.lettner the 31 Mar 10 at 19:18.

Add a button which assigns the most useful and common rights to the selected item (recursively if it's a directory).
that would be rw-r--r-- for files and rwxr-xr-x for folders.

this would be very useful for example if you copy files from lesser advanced filesystems like the ones used in windows which don't have rights management (they are often set to wrong values like 777 then)

just one button - one click - which sets the default rights. so the user is safe and doesn't even have to know anything about rights management.

Add a button which assigns the most useful and common rights to the selected item (recursively if it's a directory). that would be rw-r--r-- for files and rwxr-xr-x for folders. this would be very useful for example if you copy files from lesser advanced filesystems like the ones used in windows which don't have rights management (they are often set to wrong values like 777 then) just one button - one click - which sets the default rights. so the user is safe and doesn't even have to know anything about rights management.

Written by Darwin Survivor the 31 Mar 10 at 22:21.

Instead of using
Owner: Read, etc
Group: Read, etc
Others: Read, etc

Why not list the actual owner/group of the file?
Owner (Joe): Read, etc
Group (users): Read, etc
Others: Read, etc.

Instead of using Owner: Read, etc Group: Read, etc Others: Read, etc Why not list the actual owner/group of the file? Owner (Joe): Read, etc Group (users): Read, etc Others: Read, etc.

Written by Penguin Guy the 1 Apr 10 at 16:31.

Use the checkbox-grid idea as in solution #1, but remove 'Set user ID', 'Set group ID', and 'Sticky'.

Use the checkbox-grid idea as in solution #1, but remove 'Set user ID', 'Set group ID', and 'Sticky'.

Written by tommynz1975 the 3 Apr 10 at 05:30.

I am not to sure what the poster ment.

But to be able to edit users in each group when one brings up the properties window shown in solution #1

Maybe having an unlock button on the properties dialog box, like with network settings would be good.

This could solve the other issue some have of, I am the only user but have no access to my usb drive, cant change properties.

I am not to sure what the poster ment. But to be able to edit users in each group when one brings up the properties window shown in solution #1 Maybe having an unlock button on the properties dialog box, like with network settings would be good. This could solve the other issue some have of, I am the only user but have no access to my usb drive, cant change properties.

Written by lfaraone the 3 Apr 10 at 17:30.

Building off solution one, we should also add logical grouping, which will allow the user to follow associations between the preferences in the grid more easily.

Building off solution one, we should also add logical grouping, which will allow the user to follow associations between the preferences in the grid more easily. <img src="http://img265.imageshack.us/img265/9108/newpermissions.png" />

Written by braiam the 8 Apr 10 at 06:45.

As in the Solution # 3, we can´t change user right of a file/folder if we are not root, this should change with a Bottom that read "Become root" and reload the box, Solution # 1 are usefully to know current access permitions and with Become Root butoom change it. Set SID and text migth be in a advanced section.

As in the Solution # 3, we can´t change user right of a file/folder if we are not root, this should change with a Bottom that read "Become root" and reload the box, Solution # 1 are usefully to know current access permitions and with Become Root butoom change it. Set SID and text migth be in a advanced section.

Written by Tatsel the 12 Apr 10 at 06:53.

I agree, the default one confused me long time (and still does), so I am proposing the advanced view, the "Become Root" button, the "default permissions" button, for dual(or more)-booters, as example and the current Owner/Group.

About #6, I would rather put it under a button that open a small dialog (or anything similar) because:

1- This is more advanced features that new users should probably not mess with;

2- the permission dialog will be rather big even without those last options. We don't all have 32'', HD computer screens.

I agree, the default one confused me long time (and still does), so I am proposing the advanced view, the "Become Root" button, the "default permissions" button, for dual(or more)-booters, as example and the current Owner/Group. About #6, I would rather put it under a button that open a small dialog (or anything similar) because: 1- This is more advanced features that new users should probably not mess with; 2- the permission dialog will be rather big even without those last options. We don't all have 32'', HD computer screens.

Written by Penguin Guy the 29 Aug 09 at 18:04.

Color the links the same as when you are viewing posts. This will make editing text less confusing.

Color the links the same as when you are viewing posts. This will make editing text less confusing. <img src="http://dl.getdropbox.com/u/1217030/Ubuntu%20Brainstorm/UF%20Link%20New.png">

Written by Penguin Guy the 31 Aug 09 at 11:50.

Create a shared folder for these files so that any applications that work with code can use these files rather than their own. There should be a system-wide folder at '/usr/share/syntax/' and a folder for each user at '~/.syntax/' (so they can change the default coloring).

The syntax files should not specify a color themselves, they should specify a type (text, comment, variable, etc) which will be assigned a color in '~/.syntax/color' or '/usr/share/syntax/color'.

Create a shared folder for these files so that any applications that work with code can use these files rather than their own. There should be a system-wide folder at '/usr/share/syntax/' and a folder for each user at '~/.syntax/' (so they can change the default coloring). The syntax files should not specify a color themselves, they should specify a type (text, comment, variable, etc) which will be assigned a color in '~/.syntax/color' or '/usr/share/syntax/color'.

Written by Penguin Guy the 31 Aug 09 at 13:16.

Add a new option in Nautilus to view backup files, this can be activated if you need to recover a document, but will not get in the way when you want to find a hidden file.

Add a new option in Nautilus to view backup files, this can be activated if you need to recover a document, but will not get in the way when you want to find a hidden file.

Written by Penguin Guy the 31 Aug 09 at 13:20.

Change the 'ls' command so that you have to add a parameter to see backup files. Change the -B parameter so it will now show backup files, rather than hiding them.

Change the 'ls' command so that you have to add a parameter to see backup files. Change the -B parameter so it will now show backup files, rather than hiding them.

Written by Penguin Guy the 19 Aug 09 at 16:39.

Possible Uses:

Images
o 'Open' - 'Photo Viewer'
o 'Edit' - 'Gimp'

Sound Files
o 'Open' - 'Rhythmbox'
o 'Edit' - 'Audacity'

HTML
o 'Open' - 'Firefox'
o 'Edit' - 'Bluefish'

---------------

In the 'Properties' -> 'Open With' menu you should add options to disable the Open or Edit buttons for certain files (most people read text files through a text editor so there would be no need for the 'Open' option on them). It would of course, be possible to assign an editor to the open button, but that's up to the user.

Possible Uses: Images o 'Open' - 'Photo Viewer' o 'Edit' - 'Gimp' Sound Files o 'Open' - 'Rhythmbox' o 'Edit' - 'Audacity' HTML o 'Open' - 'Firefox' o 'Edit' - 'Bluefish' --------------- In the 'Properties' -> 'Open With' menu you should add options to disable the Open or Edit buttons for certain files (most people read text files through a text editor so there would be no need for the 'Open' option on them). It would of course, be possible to assign an editor to the open button, but that's up to the user.

Written by Darwin Survivor the 20 Aug 09 at 17:56.

I find needing to chose between opening and executing a file *after* clicking it to be annoying. The context menu should have 3 options.
-Open/View
-Edit
-Execute

Of course, each option would only appear if the action were possible such as not having the execute option for a jpeg or any object without +x in the permissions.

Every file has 3 permission levels (rwx), why not have 3 ways of opening it via context-menu?

I find needing to chose between opening and executing a file *after* clicking it to be annoying. The context menu should have 3 options. -Open/View -Edit -Execute Of course, each option would only appear if the action were possible such as not having the execute option for a jpeg or any object without +x in the permissions. Every file has 3 permission levels (rwx), why not have 3 ways of opening it via context-menu?

Written by Penguin Guy the 21 Aug 09 at 13:19.

Possible uses:

Images
o 'View' - 'Photo Viewer'
o 'Edit' - 'Gimp'

Sound Files
o 'Play' - 'Rhythmbox'
o 'Edit' - 'Audacity'

Scripts
o 'Execute' - 'Sh'
o 'Edit' - 'Vim'

Archives
o 'Extract' - 'Archive Manager'
o 'Browse' - 'Archive Mounter'

---------------

Simply switch 'Open' and 'Edit' for more descriptive words (such as the above) if needed. Although this has no practical effect, it will certainly add to the depth of the user experience. Inspired by michele74.

Possible uses: Images o 'View' - 'Photo Viewer' o 'Edit' - 'Gimp' Sound Files o 'Play' - 'Rhythmbox' o 'Edit' - 'Audacity' Scripts o 'Execute' - 'Sh' o 'Edit' - 'Vim' Archives o 'Extract' - 'Archive Manager' o 'Browse' - 'Archive Mounter' --------------- Simply switch 'Open' and 'Edit' for more descriptive words (such as the above) if needed. Although this has no practical effect, it will certainly add to the depth of the user experience. Inspired by michele74.

Written by Wim the 24 Aug 09 at 15:06.

Why limit the user to predefined 'Open With' options? Allow the user to rename and add alternatives. It would probably be nice to have some reasonable defaults though (such as in idea #3). For example:

Default HTML
o 'Open' - 'Firefox'
o 'Edit' - 'Bluefish'

User-Configured HTML
o 'Open' - 'Epiphany'
o 'Edit' - 'Emacs'
o '2Text' - 'html2text'

Why limit the user to predefined 'Open With' options? Allow the user to rename and add alternatives. It would probably be nice to have some reasonable defaults though (such as in idea #3). For example: Default HTML o 'Open' - 'Firefox' o 'Edit' - 'Bluefish' User-Configured HTML o 'Open' - 'Epiphany' o 'Edit' - 'Emacs' o '2Text' - 'html2text'

Written by RomanIvanov the 24 Aug 09 at 19:12.

Iy is great idea to have few applications to use for one type of the file. But It should be triggered by Advanced settings items. No changes by default.

Iy is great idea to have few applications to use for one type of the file. But It should be triggered by Advanced settings items. No changes by default.

Written by mrpitchfork the 7 Sep 09 at 22:55.

The default app for opening a file should change based on the last choice used to open the file from the context menu.

The default app for opening a file should change based on the last choice used to open the file from the context menu.

Written by Penguin Guy the 13 May 09 at 19:39.

Next to the download link on the website put something like: 'Please consider seeding Ubuntu after you have downloaded it.'.

Next to the download link on the website put something like: 'Please consider seeding Ubuntu after you have downloaded it.'.

Written by Penguin Guy the 13 May 09 at 19:44.

Once the distribution has finished installing open up a prompt asking the user to consider seeding; have an 'OK' box that will do it all automatically.

-1: Personally I think this is a bit overkill; but I'll let you guys vote on it.

Once the distribution has finished installing open up a prompt asking the user to consider seeding; have an 'OK' box that will do it all automatically. -1: Personally I think this is a bit overkill; but I'll let you guys vote on it.

Written by Penguin Guy the 2 Apr 09 at 18:10.

When you click on a link to a file/folder on a device that is not mounted, Ubuntu should attempt to mount the device and follow the link. Ubuntu should only bring up an error message if the device cannot be mounted or the link cannot be followed. To make this possible, links made to external devices should not start with the mount point '/media/.../', but the device ID '1A7B482C:///'.

When you click on a link to a file/folder on a device that is not mounted, Ubuntu should attempt to mount the device and follow the link. Ubuntu should only bring up an error message if the device cannot be mounted or the link cannot be followed. To make this possible, links made to external devices should not start with the mount point '/media/.../', but the device ID '1A7B482C:///'.