I've been using 2.0 since wicket first branched, and remember being really
excited about some of the things the constructor change would allow me to
do, such as perform all kinds of ajax magic. It turns out that wicket ajax
support has become so sophisticated I haven't had to do any of those things,
so downgrading shouldn't cause me any loss of features. Reverting the
constructor change will probably cost me a few days, but the end it will
probably be worth it. I have noticed recently a somewhat troubling trend.
You guys used to be very disciplined about adding features to 2.0 and then
backporting them to the other branches. Now it seems like new features are
developed in any branch and then maybe or maybe not ported to the others.
That's definitely a train wreck waiting to happen, and it is understandably
a source of misery for all of you. Dump it if you need to, your collective
happiness is more important to me :).
It would be great to have a definitive list of 2.0 features that will be
lost, so I can plan ahead for any redesign if necessary. For example, I've
used generics (with mixed feelings) and covariance extensively, so these
will probably be more painful to lose than the constructor change. Will
these be jettisoned as well?
thx,
jim
On 3/6/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
Hi,
We (Wicket's developers) are having some discussion over 1.3 vs 2.0
and how difficult it is as a nun-funded project to spend so much time
synchronizing the branches.
A major issue in the discussion is that not everyone is convinced
anymore that the constructor change in 2.0 is for the better. There
are pros and cons for sure, but we want to get your opinion on this.
Please help us out giving your opinion. We want to know:
1) Who uses 2.0 for serious projects?
2) What do you think of the constructor change? Do you prefer 1.3's
add style or 2.0's style of passing in the parent construction time.
3) If we would ever backtrack on the constructor change (*if*, don't
panic for now) how much trouble would that give you?
Please don't be shy giving your opinion. This is an important issue in
the future development of Wicket.
Regards,
Eelco
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
