[RFC] Context-Menu Handling in KDevelop4

[Jens Herden]

> That's why I'm for a combined aproach: What about having the 5 most used
> entries at the top of the menu, then a separator, and then the per-plugin
> sub-menus?

While I can see the benefit of being a little faster with often used actions I 
do not like your idea.

1. having changing items in the menu is bad in my opinion, especially at the 
top. It will force people to re-scan the menu again and again. Static menus 
get known by people and they will not re-scan them again.

2. Since the name of the action is defined inside of the plugin you can have 
two actions with the same name. If they are in a submenu you know the context 
but if they pop up on top of the menu you can not know anymore what they are 
doing.

Jens
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20070509/970f05ab/attachment.sig>