I agree that it is not always clear where to find it but at the end there are only two (three) possibilities. I don't like the idea of a giant application class. I still like the original intent: easy (integer, string, boolean) parameters in ApplicationSettings and more complex parameters like factories in Application.
Juergen On 1/1/06, Jonathan Locke <[EMAIL PROTECTED]> wrote: > > Maybe we should get rid of ApplicationSettings and ApplicationPages > entirely and just have one gigantic Application class. It's a little > ugly, but at least you know where to look for things! > > My original intent with this class was to just put all the simple values > in a settings class. But now we've got strategies and other complex > objects in there and I'm not sure users are going to be able to make any > logical sense of the division anyway. > > What's your vote? I think I'm +1, but I could be convinced to change my > mind. > > Best, > > Jon > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Wicket-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wicket-develop > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
