+1
Jonathan Locke wrote:
please don't be too freaked out if my checkin today doesn't resolve every last issue (although the unit tests run fine). i'm in the middle of refactoring a lot of stuff and just wanted to get in sync.
one result of today's refactor effort is that class resolution and page creation are much simpler and are now controlled through two different interfaces: IClassResolver and IPageFactory. a huge amount of code and complexity went away and little seems to be affected.
what is going to affect more code, but seems necessary is the refactor i'm doing on ApplicationSettings. in the end, there are going to be three classes instead of one because this class has grown out of control: ApplicationSettings, ApplicationPages and ApplicationContext (i'm open to some better name for this since i hate the word Context!). basically the hope is to get ApplicationSettings back to just holding a reasonable number of settings that affect the functioning of wicket. things like getResourceWatcher() are simply not settings and don't belong in ApplicationSettings. therefore i'll be making ApplicationContext for this kind of stuff... make sense?
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
