Re: pluggable context menus ...

[Manuel Clos <llanero eresmas net>]

bordoley msu edu wrote:

> Manuel Clos  said:
>
> >My idea is to have a "mime type" entry just after "open with..." that
> >has all these options. So the menu will always be there and will never
> >get empty.
> >
> >So, for "image" mime type you get:
> >
> >open
> >open in new window <--- remove this one please ;)
> >open with...
> >image ----> open  <--- this one is bold because is the default action
> >                    print
> >                    rotate
> >                    resize
> >                    show notes
>
> The HIG also states that context menus should not have sub-menus so 
> either way
> is a comprimise. also why would you have open in the context menu, I would
> find this rather confusing to have two open menu entries. Also in 
> regards to
> archives, I don't think they should have any menu entries. We need 
> seemless
> integration of archives into nautilus (via vfs) anything else is 
> masking the
> problem.

Well, just because it is the _default_ action. But yes, I agree with 
open not being there.
So we already have submenus in the context menu. Adding a new one is no 
problem. I much prefer adding a submenu to menuitems not being always in 
the same place. Anyway, this is just my point of view.
Even if you have seemless integration of archives in nautilus, you want 
a "extract to ..." item, so you are not forced to clicking into the 
archive, waiting for nautilus to uncompress it (say a tar.gz) then show 
the contents (mime-type icon loading, long directory loading), then 
select all, copy and paste where you want the files (copy data already 
extracted).
When you just want the tar.gz archive unpacked, a simple uncompress here 
is very convenient.
So I think we should include all mime-type options under the same 
submenu, so the main context menu never gets cluttered.
--
Manuel Clos
llanero eresmas net

TCPA y Palladium: http://bulmalug.net/body.phtml?nIdNoticia=1398
TCPA and Palladium: http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html