simplified menu editing [Re: what's going on with menus?]
- From: Mark McLoughlin <markmc redhat com>
- To: Calum Benson <calum benson sun com>
- Cc: Desktop Devel <desktop-devel-list gnome org>
- Subject: simplified menu editing [Re: what's going on with menus?]
- Date: Thu, 20 May 2004 19:32:09 +0100
Hi Calum,
On Thu, 2004-05-20 at 17:02, Calum Benson wrote:
> On Tue, 2004-05-18 at 18:13, Mark McLoughlin wrote:
>
> > 5) Write a simple menu editor for the panel which allows you to
> > enable/disable menu items - it would just generate a .menu file in
> > .config with a set of <Include>/<Exclude>s[2].
>
> Just to kick off some discussion, then, here's a quick sketch of what's
> probably about the simplest useful GUI you could have to meet this
> requirement:
>
> http://www.gnome.org/~calum/usability/specs/menu-edit/
Thanks much for taking a look at this. It looks like a good start. Some
comments:
+ You're right, we can't re-order the items
+ I think we can make something like this work nicely, but only for
entries that initially (before any editing) appear in the default
menu - i.e. when you start the app for the first time, there will be
no disable items.
The problem is that, I don't think there's any way we can easily
figure out where an item which is disabled by the system wide menu
would go if it *wasn't* disabled. Perhaps we can do compare the
layout ignoring <Excludes> with the normal layout. It needs some
thought ...
+ Allowing entire menus to be disabled is a good idea IMHO. I'd
imagine it would be common for people to disable the Accessibility
menu, for instance. The other approach is just that the menu doesn't
appear if its empty.
+ Instant apply seems fine to me ...
+ I'm not sure why we'd want the "Show All" thing. It sounds like it
would significantly complicate the interface.
Thanks,
Mark.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]