I used Umbrello UML on linux to draw the diagram, by hand. For the model refactoring, I know this won't be easy, it's the very core of Wicket after all. I thought it could be part of Wicket 2.0 or something, in the long term. But I think it has become really necessary.
Resources too could benefit from some refactoring. For example, the I18N system works great to pick a resource according to the Session's Locale (ex: style_en.css, style_fr.css ...) but I can't get the Style (also set in the Session) system to work on non-packaged resources (typically, picking style_blue.css over style_normal.css in the <webapp_root>/css/ directory). And the resource finding algorithm could benefit from a pluggable Strategy pattern, for example to group localized resources by directory instead of appending the locale to their name (/css/en/style.css instead of /css/style_en.css). I know this will require some hard work too. Again, maybe for an hypothetical Wicket 2.0 ? For now I'm a semi-advanced user of Wicket - I use it, blog about it, write components - and I've been diving into the source code for a few weeks. I'll see if I can submit patches or ideas as soon as I feel confident with the current code. BTW, how can I draw the attention of the core team to this thread ? I'd love to have their opinion on all this. Olivier On Fri, Oct 16, 2009 at 11:30 AM, Michael Mosmann <[email protected]>wrote: > Hi, > > > I do see my image attached to my previous post - or is it just me ? > > maybe it's just me not seeing an image.. who knows? > > > If you really can't see it, I uploaded it here : > > http://olivier.croisier.free.fr/wicket/models.png > > thank you.. > > did you do this by hand or is there a good tool to do this? > > > About the models, for example : > > - ComponentPropertyModel is not in the same hierarchy as > > AbstractPropertyModel. > > - StringResourceModel is not a ResourceModel > > And so on. > > ok.. > now i know what you mean.. > hmm.. it's worth a look, if it does make sense.. > > > I know there are many justification to this, but I think the whole Model > > hierarchy should be refactored and simplified. > > if it is a way to achive this, everybody is with you:) > > > If I may do some suggestions, ... > > ........ > > ....... > > Please let me know what do you think about this ? > > I think, this question should go to some of the core member:) .. > I know, there is a lot of discussion around this model stuff.. > > mm:) > > >
