[RFC] Context-Menu Handling in KDevelop4
David Nolden
david.nolden at art-master.de
Wed May 9 11:05:11 UTC 2007
On Wednesday 09 May 2007 12:29:35 Andreas Pakulat wrote:
> Then for now just lets ignore this. The algorithm that will create the
> menu will not be subject to binary compatibility issues at all so we can
> always change it later on...
>
> Andreas
Ok then if the sub-menu Idea wasn't accepted, how do you(thereby I mean all
who didn't like the dynamic Idea) want to address these problems?
1. The KDevelop-3 editor-context-menu is far too long
2. It mainly contains entries that I never use, and partially that I don't
even want there
I'm open for any solution, but I think the problems should be addressed,
because after all KDevelop-4 should be BETTER then KDevelop-3, not a Qt4
rewrite of it.
It is especially important because the count of potential context-menu entries
will become even bigger in kdevelop-4, just think of teamwork, the
baskets/file-sets, hopefully refactoring, etc.
Auto-hiding is inacceptable of course, as well is a scrolling menu.
greetings, David
More information about the KDevelop-devel
mailing list