KDevelop UI cleanup initiative

Paul Drummond paul.drummond at dsl.pipex.com
Tue Jun 1 21:42:05 UTC 2004

> 3. The toolbar mess.
> We have a lot of bugs related to the toolbars (for instance:
> http://bugs.kde.org/show_bug.cgi?id=79793). I have no idea if we're doing
> something fundamentally wrong somewhere or if the framework is busted, but
> we sorely need someone who understands this issue to take a look at it.

IMO one of the most confusing things is the duplicate back/foward buttons for 
code and documentation.  At the very least, the documentation buttons should 
have different icons, but it would be far better to merge the functionality.  
Is it necessary to have seperate back/forward for code and documentation?  
Wouldn't it be more intuitive to just have a single history for both?  

Also, when you switch from a document to a editor window, the change in the 
toolbars is very messy.  Not sure how to fix this, but it really makes me 
wonder whether merging document-sensitive buttons in the main menu is worth 
it.  How to users benefit from this inconsistent adding and removing of 

Would it not be far more intuitive to have a seperate toolbar for each editor 
window and keep the main menu free to store "main" buttons?  This approach 
would also fix the back/forward issue above because each window would have 
it's own toolbar.

More information about the KDevelop-devel mailing list