Bloated nautilus contextual menu
|Project:||Project : Nautilus Actions|
Problem submited on gnomefiles.org comments :
Context menu bloat By Eugenia (IP: ---.hsd1.ca.comcast.net) - Posted on 2005-09-08 12:52:10 -- Please do not place the actions on the root of the nautilus context menu. This is incosistent with the menu each time, and it adds up bloat. The Actions should have their own sub-menu IMHO.
Re: Context menu bloat By GrumZ (IP: ---.embl-grenoble.fr) - Posted on 2005-09-08 14:34:02 --- Yes, you're right, it can became quickly bloated. If we look at the HIG, it say not to add more than 10 items in a popup menu but it also advices not putting submenu. For menu in general, it advices not creating a submenu with less than 3 items. So as a compromise, I can try to create a submenu when there are more than three configured actions for a selection. What do you think ?
RE: Context menu bloat By Eugenia (IP: ---.hsd1.ca.comcast.net) - Posted on 2005-09-08 14:35:44 --- No, this is even worse!!! You see, having some actions somtimes on the root and sometimes on submenu is really bad usability as it is not consistent. IMHO, it should always be a submenu, in this particular case.
Don't really know what to think about this !? :-/
|#1 submitted by GrumZ on Thu, 2005-09-08 23:29|
Another comment on Gnomefiles.org from one of the nautilus maintainers postponed the resolution of this issue for at least 6 months :
Nautilus submenu support By Christian Neumair (IP: ---.dip0.t-ipconnect.de) - Posted on 2005-09-08 21:02:38 --- Sorry to disappoint you guys, but nautilus extensions (like nautilus-action) don't have any chance to use submenus (yet). It is scheduled  for Nautilus 2.14, though.  http://bugzilla.gnome.org/show_bug.cgi?id=314579
|#2 submitted by Anonymous Georges on Sun, 2005-09-11 11:36|
If I may voice my opinion, I am cardinally opposed to Eugenias' suggestion. Nautilus-Actions is a power-user tool and as such should not force something on the user.
What would be best, when subfolders finally become available to extensions, is to let the user build exactly the hierarchy she wishes. She could put all actions into the root menu, create subfolders for the actions or any combination of these. Basically a right-click menu editor.
And if that is possible, let user disable built-in nautilus menu commands as well. I'll give you an example - I never use the trashcan and have activated the Delete option in the menu. Now I would like to get rid of the Move to Trash option.
In general - a power-user tool should have some nice defaults, but give as many options as possible.
|#3 submitted by GrumZ on Sun, 2005-09-11 11:48|
Yes, it is a good idea. I thought about this possibility too.
For the built-in functions, I don't think that I can interract with them from an extension. If it is effectively not possible (must be verified first), maybe it would be a good idea to report a feature request on nautilus' Bugzilla.
BTW, all opinions are welcome until nautilus 2.14 release.
|#4 submitted by Anonymous Georges on Mon, 2005-09-12 01:01|
> BTW, all opinions are welcome until nautilus 2.14 release.
I'm a little lazy, can you give a link where I can file a feature request for this (allow messing with menu items from extensions)?
|#5 submitted by GrumZ on Mon, 2005-09-12 08:57|
Sorry, I won't because first we have to check if it is possible or not. I'm not sure it is or not, and last time I asked somebody to fill a bug on nautilus bugzilla, the problem was in my code.
So please don't fill any request on nautilus bugzilla unless somebody has checked that it is not already possible.
thanks in advance
|#6 submitted by GrumZ on Thu, 2005-10-06 13:40|
A quick note about this problem. In fact, the 'bloat problem' is not as critical as for example with G-Scripts (AKA nautilus scripts). As they appear in a contextual manner, you can have a hundred configs without having more than three or four items per selection. If you set up good conditions for your configs, you should not have too much bloating in fact.
|#7 submitted by GrumZ on Mon, 2006-01-02 18:26|
Bug transfered into Gnome Bugzilla :