We would like mainly to: 1) use TreeTables in
DebuggerWindow 2) change Output Window to
use tabs 3) reorganize the Debug menu and
Toolbars 4) redesign content of views
In the "Debug (full)"
toolbar, the "continue"
button is placed right next to the
"start" button. This has
two problems: 1) The start and
continue icons look almost
identical, and are therefore easy to
mis-identify 2) The continue button
seems unnaturally far away from the
"pause" button (since the
two are closely related, it would
seem they should be close
together).
I'd like to suggest that the
Start button be moved over to be
alongside the Pause button so as to
solve both of the problems just
mentioned.
It would perhaps be useful to add a
Filesystems tab to the debugger
window (or, conceivably, add the
debugger window to the explorer?) so
users could get at their files from
in the debugging workspace easily.
Reorganize the views in the debugger
window so that there is more of a
"hierarchical" flow of the
views from top to bottom.
Specifically, arrange these in the
order: Session, Threads, Stack,
Variables, Watches, Classes,
Properties
Allow control of the
selection mode (choices in
swing are
SINGLE_TREE_SELECTION,
CONTIGUOUS_TREE_SELECTION,
DISCONTIGUOUS_TREE_SELECTION)
from the TreeView APIs.
there should be some button
in treetable title bar. this
button will open some
customirer dialog with list
of all possible columns.
user can select visible
columns here. feel free to
ask me for more details ;))
there are "buttons
like" cell renderers
used by default in
treetableview. we should use
some standart - windows like
(with white background). it
will be better - believe
me...
It might be useful to have a way for
users to follow references in the
variables and watches window by
clicking on hyperlinks rather than
by opening tree nodes. Links might
also be used on the names of data
types (which could probably use the
MDR to display the class
definitions, and so on) and things
like that.
JKD 1.4 contains support for Fix&Continue
called HotSwap. We plan to support it in our
UI. Minimal requirements: 1) simple action
which reloads all classes for current source
2) solve problems with current position in
reloaded class (Pop Frames)
