I asked kind of this question maybe one month ago without replies. Glad to see someone else ask it.
I'm working on my first
Java project right now. The forms are rather complicated. And I think the code is made far more complicated by the use of inner classes.
I think it makes it far more complicated to debug the app, get an idea of the process flow by quickly looking at the source code, etc.
I found some swing examples elsewhere on the net where the author said to get used to inner classes as they are used liberally thru-out by Java programmers. But I just don't find that to be an acceptable statement.
I asked one of the better Java programmers the purpose of inner classes when .Net added the feature to the 2.0 release. His answer was that it allows for programmers to be lazy.
Does the book mentioned elsewhere, "Java Desktop Live" discuss methodologies for architecting complicated layouts?