>Everything is going smoothly. I wondered if the following features
>exist somewhere and I just can't find them.

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
> 1. viewing the JavaDoc for classes in rendered form.
I'm not exactly sure what you mean here, but Ctrl+Q (Quick JavaDoc) or
the full Shift-F1 (launch JavaDoc in browser) seem appropriate, for
classes/methods/just about anything.
> 2. getting a summary listing like the Eclipse problems panel of all
> outstanding syntax errors.
I don't know Eclipse, so I can't say for sure, but I don't recall a
feature like this.
I can't imagine why I'd need it though, error highlighting in the RHS
gutter and F2 / Shift+F2 navigation seem like plenty to me. How many
errors at a time are you writing? ;-)
--
Shane
Roedy Green - 03 Mar 2006 01:49 GMT
On Fri, 03 Mar 2006 01:03:56 GMT, Shane Petroff
<shane_petroff@yahoo.ca> wrote, quoted or indirectly quoted someone
who said :
>I can't imagine why I'd need it though, error highlighting in the RHS
>gutter and F2 / Shift+F2 navigation seem like plenty to me. How many
>errors at a time are you writing? ;-)
I change something and it creates errors far away, e.g. change a
Button to a JButton.
My eyesights is not good. Scanning for those little squiggles does not
work well. I end up doing compilations to find the errors which are
very slow in IntelliJ for some reason. It must have a way of unloading
the compiler after every use.. The Eclipse way is there is a summary
"problems" panel When that window is empty, you know you have nailed
them all. Further clicking on one line takes you direct to the
problem.
I think the key will be using f2 to find them.

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.