Basically, the question is: should the right-click context menu be selection-oriented or item-oriented? Currently it is item-oriented, where the rest of the application is selection-oriented.
Now that I think of it, item-oriented menu makes a lot of sense. It's a way to do something to one object only, without changing the selection. For example, it would be useful to have commands like:
- Select/Deselect: Object (would work the same as shift-click, command name depends on whether the clicked object is selected or not)
- Select/Deselect: Object in Group (same as shift-ctrl-click)
- Object: Properties (applied to clicked object regardless of selection)
- Object in Group: Properties
- The most useful commands specific to the object type, such as Object to Path for non-paths, Stroke to Path for objects with visible stroke, Not Rounded for rects, Make Whole for ellipses (if applicable), Unlink/Select Original for clones, etc. Also: Remove Stroke, Remove Fill (useful but not yet implemented as a separate command) etc.
However selection-oriented commands also need to be present, but in a section of their own after a separator. These may include relevant dialog openers: Text and Font if only text object(s) selected, Fill&Stroke for everything except clones, etc. These need to be selection-oriented because the corresponding dialogs are selection-oriented. When more than one object selected, this section would also contain group/ungroup, booleans, combine/break apart. Commands that may be applicable to both separate objects and selection (such as Copy) should also be here and work on selection, otherwise it may become confusing.
As for Undo/Redo, I don't think these are appropriate for the context menu at all. Any commands that are not directly applicable to an object or selection should be removed from the context menu.
So, overall, lots of useful logic may be implemented in this menu, so that opening it will at once give you lots of useful information on what's under mouse and what's selected, even if you do not call any of its commands. Most of this logic is already implemented around the codebase, you just need to gather it all in one place.
_________________________________________________________________ MSN Premium includes powerful parental controls and get 2 months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI...