It's a design philosophy ... with its pros and cons. The risk of
creating a uber class is that you loose touch of what configuration is
relevant to what component.
But in fact, the Configuration class allows you access to all the
different bits, the Controls, the Builders etc ... so that
I see, no problem. That can be also solved with documentation specifical on
what can be configured and what the defaults are I think. The default
values could be also documented in Javadoc (I know, I don't use that very
much too).
On Tue, May 20, 2014 at 8:48 AM, Mauro Talevi
