Bear Bibeault wrote:Most of my Java projects have had thousands of classes. It needs more than two levels to keep that organized.
Phil Patterson wrote:I guess you just use public classes even if they're only used in one package other than their own?
I am trying to go with a design where each package holds one main public class that allow communication between everything else and several supporter package-private classes that handle most of the actual logic.
sometimes one particular part of a role is very complex, and I feel like I want a special inner package just for it. There are several things I could do, put everything in a single huge class file, make multiple class files and just have them reside in the same package with everything else, maybe name them something that will indicate they all handle that one aspect of the role. What's usually the best option in that case?