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

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

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=144526         




------- Additional Comments From muntyan math tamu edu  2007-04-22 23:38 -------
There are bunch of problems. The screenshot shows that the variables view is very \
small, or, if you make it bigger, the editor becomes very small so stepping in \
debugger becomes worse. And you need to close bottom pane to get the variables view \
expand vertically - while in old UI you detach it and you get a whole window, which \
you can resize nicely. Clicking-and-closing is more about file selector (it's totally \
counter-productive to have to close the file selector after you open a file, it may \
seem a minor thing, but it is not) and frame stack views - I click a function in the \
backtrace and I need to see the code, to read it. When (*if*) I wanted frame stack \
view not to close, I simply used the "sticky" button. It's not like I do stupid \
things ("editing while debugging") and suffer because of my sillyness. All in all, \
the old detachable panes were so much much better than what's there now. It was a \
wonderful invention which let you use the panes in multiple ways depending on what's \
convenient at the moment. What is there now is just dumb UI intended to be used on \
huge screens where three hundred pixels is no problem (and even if I had big screen, \
probably I'd be irritated by the fact that variables view is very tall and narrow, \
you simply can't get it in a separate window of appropriate size). Having implemented \
such a paned thing, I must say it's not that hackish and hard (don't know how it's in \
QT though). It is hard, it is nasty, you have to stack windows on windows, have \
different modes for "floating" and "normal", but the benefits are way more important \
than the fact that UI code is more complicated than when you have dumb ((left + \
middle + right) + bottom) model. Oh well, just wanted to stress that old kdevelop UI \
is *very* good, even if aunt tilly doesn't know how to use it.


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