[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 144526] UI totally screwed up
From:       Yevgen Muntyan <muntyan () math ! tamu ! edu>
Date:       2007-04-22 23:32:01
Message-ID: 20070422233201.17204.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=144526         




------- Additional Comments From muntyan math tamu edu  2007-04-23 01:32 -------
Shortcut to close file selector: I *have* to use mouse to select a file in it, \
therefore I simply use mouse without keyboard to open a file, so having to press \
magic combination to close File Selector after double-click is not that convenient \
(and learning meaningless Alt-1 shortcut to close the pane after years of automatic \
closing is even harder).

If I move variable view to the bottom, it gets too small vertically (not a surprise I \
guess).

"but what is really hard is having toolviews that are not detached but cover the main \
widget while open and the automatic hiding. At least, thats what our UI guy and TT \
say." - that is not hard. It may be hard to due to reasons like "we can't change how \
it's implemented" and similar, but technically all you have to do is to create pane \
window on top of the window which contain main child (the editor). Then you get \
floating for free. Of course you have to take care about closing it when child widget \
gets focus, etc., you have two modes in one widget, it is not pretty nice, but it is \
not that hard. Alt-C is weird, but it's functional!

As to bugs, kdevelop crashed on closing/opening a project before, and crashes now. I \
never experienced crashes due to the panes. I mean, there were bugs, there are bugs, \
but the new UI is more stable only if you mean it has less features (so less bugs). \
And the old UI wasn't too buggy IMHO. Not saving size and position is a bugger, \
indeed; but better old UI not saving anything (== three clicks and three drags per \
session to set it up) than new UI where you simply can't do what you need.

Come on, if you made a strategic decision to use this new UI then it's your decision \
and I bet it's a right decision, since code maintainability alone is too important to \
give it up for more convenient UI. But don't say that new UI is cool, or better than \
the old one, or more stable :)


[prev in list] [next in list] [prev in thread] [next in thread]