I'm told by Igor that I missed a discussion on this earlier. I'm fine
with keeping ApplicationSettings, but there needs to be a logical
division between ApplicationSettings and Application that doesn't exist
right now.
Why does ApplicationSettings hold complex objects like stategies
(sometimes, anyway)? I originally was thinking of it as a place to put
simple settings values like booleans and Strings... all the complex
pluggable stuff would be in Application.
Thoughts?
Jon
Jonathan Locke 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_id=7637&alloc_id=16865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
