Menu-Structure

[Amilcar do Carmo Lucas]

On Wednesday 17 February 2010 10:00:25 Vadym Krevs wrote:
> 1. Very often you said that you use the keyboard most of the time, and
> don't want to use the mouse. Then why care so much about the menu
> structure? After all, it exists primarily for those users who don't
> use the keyboard so much or who are trying to discover how to perform
> a particular task.
Sorry, I am a developer but I mostly use the mouse. I love the new layout.
So again you are wrong here.

> 2. Why is "Find in files" hidden under Navigation? Every other
> IDE/editor places this menu next to Find/Replace.
Find in files does NOT edit nor change the file in any way. But it does allow 
you to navigate in the code.

> 3. The new Editor menu is, well, a waste of screen space for lack of
> better words. You open it, and all you see is 3 other submenus. So you
> have to click on each submenu while trying to locate the one you're
> looking for. The whole point of having a menu is to give users instant
> visual feedback into the list of available operations via a single
> mouse click/keyboard accelerator.
OK, here I kind of aggree with you.

> 4. The primary task of anyone using an IDE is write code in files and
> manage those files. If you spend more time "managing" "projects" or
> "sessions" than working on code in files, then arguably you're using
> the wrong tool, or the tool is making what should be simple
> excessively difficult. That is why placing emphasis on the Sessions or
> Projects menus makes no sense - it is simply not the primary user
> activity in an IDE or an editor.
The primary usage for me is navigation and editing. I can achieve both
with the mouse on the editor window. I do not need any of the meues. The 
editor context menu is the only one I need 90% of the time.
And exactly those actions are the ones that KDevelop excels at.


-- 
Amilcar Lucas
KDevelop developer/webmaster