Because things like getStripWhiteSpace and things like that that er now in Settings are settings yes
But getMarkupCache() , getLocalizer(), getConverterFactory(), ect,ect are not settings but configuration things.
On 12/8/05, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hi,
Looking at Application and ApplicationSettings I feel that it is
really messy. There is no clear distinction of why setting x should be
in Application and setting y in ApplicationSettings.
I think we should simplify again, and either:
* get rid of ApplicationSettings and move al the settings to
Application. Application will be big, yes, but at least it would be
very clear to find things.
or
* move everything that is even remotely a setting to the settings
object and leave application for init
I don't know about ApplicationPages yet, but the same problem exists.
Can I have your votes please?
[ ] move everything to Application
[ ] mover everything to ApplicationSettings
[ ] I'm happy with it, don't thouch that stuff!
Eelco
-------------------------------------------------------
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&opclick
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
