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 <mauro.tal...@aquilonia.org>wrote: > 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 should be your > starting point. > > > On 19/05/2014 12:45, Hans Schwäbli wrote: > >> It seems a bit difficult to me to see which preferences can be set and >> what the defaults are. >> For example where is a class EmbedderControls which contains some of the >> preferences and defaults. >> There are more preferences like in ParameterControls, >> StoryReporterBuilder and other classes. >> What about putting them into a dedicated preferences class(es)? It would >> self document what preferences can be configured and it would be easier to >> find them. >> I am thinking about a class similiar like this: >> http://download.eclipse.org/technology/swtbot/helios/dev- >> build/apidocs/org/eclipse/swtbot/swt/finder/utils/SWTBotPreferences.html >> Maybe it could be several classes in the same preferences package >> containing all meaningful preferences to be set. The source could be a >> property file (like partly in IBM RFT) where the user could see them all in >> a central place and change them if he wishes. >> Maybe it is not a good idea, I don't know. I just have the impression >> that the preferences are a bit hard to find and spread across many places. >> > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > >
