#53 Modify compiler errors interface
The ScrollPane interface to the compiler errors is
slow and a bit awkward. There's never any need in
scrolling half way between two errors. Perhaps a
cleaner interface would be up and down arrow buttons
(with their own keyboard shortcuts) that allow for
atomic scrolling between errors.
Story: The user compiles a program with errors. The
compiler errors tabbed pane pops up and displays the
first of these errors. A count of the total number of
errors appears off to the side. The user fixes this
error and then quickly pops to the next by clicking
on the down arrow button in the compiler errors
tabbed pane. He then clicks on the up arrow button,
and the first error reappears, with the fixed text
highlighted. He clicks the up and down arrow buttons
repeatedly, scrolling through and fixing the compiler
errors in the program.
The user then learns the keyboard shortcuts and
quickly pops from error to error without switching
focus from the definitions pane.
-- Eric
Logged In: YES
user_id=431096
I definitely like the idea of "next error" and "previous error" shortcuts that can be executed from the definitions pane. Those shortcuts can be independent of any changes to the compile errors pane. I personally dislike moving away from standard control elements like scrollbars. The more we customize our UI, the more quirky and difficult to learn it will be. We may be able to achieve the same results using a standard scrollbar by controlling properties of the scrollbar or with a JTable.
Logged In: YES
user_id=429660
Your point about the dangers of customizing are well-
taken. Also, I think you're right in surmising that we can
achieve the best of both worlds in this regard.
Logged In: YES
user_id=429731
Turned out there was a duplicate request for this with a
higher priority (638268, "Compiler Error Navigation"). I'll
raise the priority on this copy a bit (since Corky has
mentioned it a few times now), and I'll close the other copy.
Another possibility to look into as we're modifying the
error interface is to group the errors in a JTree, rather
than just straight text. (Each error would be displayed in
a custom panel with the same information we have now.) The
tree would only have two levels-- files at the top, and
errors as leaves. This would improve usability by allowing
users to collapse parts of the tree they've already seen.
Charlie