Re: javagator, after using it for a month

John Richardson wrote:

>>>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.
> 
> 
> I'm talking about one file with contents like this:
> 
> public class MyPublicClass {
>     ...
> }
> 
> class Foo {
>     public void doFoo() { ... }
> }
> 
> 
> Foo won't show up at all in the Navigator, but it is there in the
> Filesystems explorer.

That was a complexity reduction effort when I was first getting
it working that I simply haven't bothered with - if there is more
than one class returned at the top level, it simply takes the 0th
tab and discards the other.  It adds quite a bit of complexity (how
to indicate which class each belongs to?) in order to support
something nobody should be doing anyway.

On the other hand, folks do have legacy sources they can't change.

Given that JDK 1.0 style classes are pretty strongly discouraged, I'm
not sure it's such a great idea to support, although since the spec
allows it, in the long run, perhaps it will get supported.  Opinions?

In the end, the Java module folks will either inherit my Java look or
write their own, so since the java module supports this, probably
Navigator will too.

-Tim