Customizable Context Menus
Posted: 06 Jul 2007 19:21
Ok, just a wish I'll throw in before the break. I've been thinking about this for a while now, and I really think it would be a pretty cool thing to have.
You know how, when thinking about adding command to various context menus, such as the List (blank area) one, or Tree items one, etc there's always the issue of space, and how those menus are already quite filled up for some.
Well, why not let the user dedcide and bring in "Customizable Context Menus" !
Just like for CKS, there would be the need to have a list of all commands available in XY (this cound include Misc. & "customizable commands"/softkeys -- see again why need it might be good to separate the name for those to "keys"
) and the user could then decide what to include on the context menus.
Thay way one could decide what should and should not be on different context menus, so not only could one get ride of items there by default that he never uses, but he could add some he uses a lots & whishes to be there, even Misc/customizable ones (eg. "Move To [D:\MyFolder]"), that are unlikely to be there by default/for everyone.
You'll probably have noticed that I said context menus, because I actually think you could even push it further that "just" the List context menu (and its Finding Tab twin) and also includes the context menu for items on List, and on Tree.
For those, there could even be the possibility of one extra "command" : Shell Context Menu. This would be the shell context menu, so one could not only decide where to add his XY'x items (before/after), but also decide to have it as a popup/sub-menu !!
For example, imagine this: For the Tree's items context menu, one could only left the XY commands, maybe adding a few of his choice, eg. add XY's Cut/Copy ones, and then have a menu that would say "Shell Context Menu", which when clicked would get the usual shell context menu for that item.
Results: Besides being able to choose/design the ctxt menu, by getting ride of the shell part the menu will show up at the speed of light, being an XY only menu.
Of course this could also be done on List, I only choose the Tree as example cause I almost never user the shell items from that menu, unlike with the List items ctxt menu.
You know how, when thinking about adding command to various context menus, such as the List (blank area) one, or Tree items one, etc there's always the issue of space, and how those menus are already quite filled up for some.
Well, why not let the user dedcide and bring in "Customizable Context Menus" !
Just like for CKS, there would be the need to have a list of all commands available in XY (this cound include Misc. & "customizable commands"/softkeys -- see again why need it might be good to separate the name for those to "keys"
Thay way one could decide what should and should not be on different context menus, so not only could one get ride of items there by default that he never uses, but he could add some he uses a lots & whishes to be there, even Misc/customizable ones (eg. "Move To [D:\MyFolder]"), that are unlikely to be there by default/for everyone.
You'll probably have noticed that I said context menus, because I actually think you could even push it further that "just" the List context menu (and its Finding Tab twin) and also includes the context menu for items on List, and on Tree.
For those, there could even be the possibility of one extra "command" : Shell Context Menu. This would be the shell context menu, so one could not only decide where to add his XY'x items (before/after), but also decide to have it as a popup/sub-menu !!
For example, imagine this: For the Tree's items context menu, one could only left the XY commands, maybe adding a few of his choice, eg. add XY's Cut/Copy ones, and then have a menu that would say "Shell Context Menu", which when clicked would get the usual shell context menu for that item.
Results: Besides being able to choose/design the ctxt menu, by getting ride of the shell part the menu will show up at the speed of light, being an XY only menu.
Of course this could also be done on List, I only choose the Tree as example cause I almost never user the shell items from that menu, unlike with the List items ctxt menu.