Optimoz RadialContext Pie Menu 1.0b3 Released
Thursday September 19th, 2002
shepard writes: "Optimoz's RadialContext pie menu version 1.0b3 has been released! Includes bug fixes and some reorganization of the interface. This is a highly recommended add-on for Moz!"
by johnlar <email@example.com>
Thursday September 19th, 2002 7:00 AM
Arg I still can't stand the submenus following me around :(
Try to think of it as a gesture with hints. Use the menu by holding the mouse button down and dragging.
There also is an option to use the radial menu only when dragging. That way you can still use 'click to open' to access the standard menu (works only under Windows).
Maybe the icons just suck but I find the menu rather confusing. One wrong move with your mouse and you are looking at a submenu with no option to go back. Also the fact that the menu moves around with your mouse is very annoying. The point of a context menu is that it appears at the point/context where you click the mouse. If you move the mouse, the context is still the same. Clicking outside the menu should just dismiss it.
The (radial) context menu should not move with the mouse. It seems you like the idea, others may share my view. Is there a way to make this configurable?
For consistency I think it should be possible to open a submenu by clicking, not just by moving out of the menu (which causes an odd jumping effect).
It would be really cool if the radial context menu could use a native OS window, like the 'real' context menu.
PS: The icons are a matter of taste, but it would be nice if they would match the skin. Currently they fit mostly to Classic (colors), but the icons itself don't. This is a bit odd. Hopefuly you find a graphics designer to do the jobs, so you can concentrate on the programming ;-)
I forgot to mention that the menus should not be cluttered. Just because there is room there is no need to include 'extra features'. In particular I refer to the tasks menu, which is only present when there is no selection active. And I am also talking about the window menu. Both menus are IMHO just not necessary. Save the room (see below for a possibility).
Is there a reason why the 'property' option is not present?
Interestingly there is a subtle difference betwen the offical context menu and RadialContext when it comes to frames and you have a selection. Mozilla will you give you acces to the frame info, whereas RadialContext has the page info. If you remove window and tab you get room for a property submenu and you can also show *always* page and frame info (the latter greyed out/disabled when not applicable).
BTW, the selection submenu is missing the 'view selected source' feature.
Doh. WHy does Mozilla remember that title? The former post should have a title of 'more comments' or something like that.
1. Context menus present a limited selection of commands for the given context. They don't gray out items.
2. I'm considering to remove the window and tasks menus.
3. There's no special reason not to have the 'property' option. I just personally don't use it too often, and I still have to get a better idea of what people demand for.
4. The frame context has a seperate item for getting info about it.
5. I'm still working on 'view selected soure'.
6. I've considered to make the submenu icons clickable. But I'm afraid some users will not discover how to access submenus 'properly'. Also having different ways to do the same thing generally slows one down. I am in fact cosidering to drop 'click to open' support entirely.
7. If an option is missing, you can always access the standard menu with the Ctrl modifier.
If people start complaining about details, I must be on the right track ;).
Maybe the should not, but they do (in Mozilla, IE, Windows, ...). But I don't insist on greying out menu items. It is just a possibility. But I am for sparing the room where the frame option would be (in non framed pages).
ad 3 & 7)
I don't use it too often myself, but It comes in handy sometime. I'd prefer to not relying on the 'official' context menu. Ideally you would not need it any more.
What opens a submenu 'properly' is IMHO a matter of style and taste. I vote for making it configurable (at least via a hidden pref in a .js file - yikes) defaulting to off for click-opens-submenu.
Yes, you are on the right track. I have it currently enabled, but wonder if I get used to the 'icon hell'. The number of icons to remember is very high :-(
I tend to find the icons act as a 'place' to click - the reference to gestures with pictures is the best I have heard! If it is an option I use commonly then it is the directions that are remembered quicker than the pictures, if it is an uncommon option then Im likely to go by the description and not the icon anyway ;-)
The icons do leave a lot to be desired. On the other hand, it is easy to replace the images. I made a pie that matches the GrayModern/Pinball themes. Basically all you have to do is replace the image files in chrome/radialcontext/content/skin and restart Mozilla. With 1.0b3, I made a semi-transparent png for the menu labels (this required editing a couple of the js files: s/gif/png/).