Igor Vaynberg wrote
>i am wondering how many of the "keep as is in trunk" votes came from
people who only imagined what their code would look like and havent
>actually hit the numerous pain points those of us who did code gainst
it hit.
I'm one of the "keep as is in trunk" users and I use 1.4 trunk from the
beginning. I use it in a big real world application. But: I am one of
the former 2.0 users and accustomed to generic Components in Wicket.
Maybe I have made my workaround strategy for some generic problems more
than a year ago.
One experience I made was that I realized that I made no use of Models
when I startet using Wicket from 1.0. Instead of having
public class MyPanel extends Panel<MyData>
public MyPanel(String id, IModel<MyData> model) {
...
I used constructs like
public class MyPanel extends Panel
public MyPanel(String id, MyData myData) {
...
like I was used to do in other frameworks. The second one was the only
way to have a typesafe treatment of MyData when Model was non generic.
It took a while to realize that the Models in Wicket are very usefull
thing and the tight Component-Model coupling leads to better
Applications
Maybe the posts like "I do not use Models" or "Only 20% or our
components have Models" come from the same background as my early wicket
adoption.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
