Re: javagator, after using it for a month

John Richardson wrote:
> I don't know if Navigator/Javagator is intended to be productized for
> 4.0 as the code stands now, or if it'll be restructured for that
> release.  But I figure I'd let you know what I've found after a while of
> using it.  

It will be restructured.  Consider the current Looks for Java a
prototype - they'll end up being a demo to teach module owners how
to write their own.

> In general it's great.  It's hard to live without it.

:-)

> 1) I've found that it's quite slow to open a new file.  NetBeans hangs
> for a while, then recovers and all is well.  During the hang I did a few
> dumps.  Most of the classes are gj parsing with what looks like
> javagator initiating the parse.  This is very annoying.

I need to find a workaround for this - the main problem seems to be
that both Javagator and the editor initiate source parses on different
threads at the same time (I moved it of AWT a week or two ago for
Javagator, to improve things a bit), and go to war.  My feeling is
that for 3.6 we're going to end up with a tightly tuned combination
of the editor playing nice with source parsing, which gets thrown
out of whack when anything else that wants a parse enters the mix.

> 2) It doesn't show non-public classes in a file.  These classes aren't
> typical, but used more often than I'd like in some codebases.

Do you mean anonymous classes?  The parser doesn't reveal them, and
I can only work with what it gives me.  If you mean there are non-public
named classes that aren't showing up, that's a bug - but I was
just using it to browse some non-public classes.

> 3) While the abbreviations seem like a great idea, I find that I just
> can't get used to them.  I end up turning them off.

It needs some work, as noted.  I've had no time since around christmas
to put time into this module, other than a few tweaks here and there.

Thanks for the feedback!

-Tim