Dear Philip, we are in the same situation. Just starting a new project, we discussed to write a generic wrapper for all the wicket classes (Model, Component, etc.). We are waiting for a generic wicket wersion now for a year. Having a genierfied wicket version (let's call it 1.4M1 or 2.0M1) wohlg make us sooo happ.
Migration to wicket 1.3 was impossible because of heavy generic usage all around our code. It's hard to imagine how to use wicket's model without generics. I totally agree with your opinion: "Quit punishing us 2.0 early adopters already". It is still a pleasuere to use OLD wicket 2.0 and it still works pretty stable. And I am sure it will be much more pleasure to work with a generified wicket 1.4/2.0 Stefan -----Ursprüngliche Nachricht----- Von: Philip A. Chapman [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 14. März 2008 22:00 An: dev@wicket.apache.org Betreff: Re: Planning Wicket Next Generation -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ++++++++++1 I've been waiting on generics since 2.0 was killed. As an early adopter of 2.0, I've been struggling with a few projects that where written against 2.0. So far, I've fought off the urge to convert to 1.3 simply because it doesn't make sense to rewrite for 1.3, then again for 1.4. Also, these projects make *heavy* use of generics and it would be a terrible pain to re-write them without. I'd rather go straight to the generics version. Quit punishing us 2.0 early adopters already. Jeremy Thomerson wrote: > I definitely don't have any votes in this, but I have several production apps > running with Wicket, and use 1.5 / generics in all of them. Has there been > any discussion of a faster release that ONLY includes generics? Last I > remember, someone had the generics patch(es) basically done, and just needed > to apply them. > > I would really like to see generics soon, but if they get put in with all the > other features for 1.4, it would be 6-9 months (at least) before I could use > them. > > Jeremy Thomerson > -- sent from a wireless device > > -----Original Message----- > From: "Johan Compagner" <[EMAIL PROTECTED]> > To: dev@wicket.apache.org > Sent: 3/14/08 4:23 PM > Subject: Re: Planning Wicket Next Generation > > Its not that revolutionairy. > For example if 1.4 was just 1.3+generics then if your project like > vocus thats already on 1.5 it would be a drop in replacement. So api > and 'feature' wise not much has happend then, only easy of development > (for most not all are fans ;)) > > On 3/14/08, Martijn Dashorst <[EMAIL PROTECTED]> wrote: >> On 3/14/08, Igor Vaynberg <[EMAIL PROTECTED]> wrote: >>> is the next release an evolution or revolution? :) i think first we >>> need to make a list of all major things we want to go into it, and >>> then decide. >> I think it counts as revolutionary: abandoning Java 1.4 is >> revolutionary I think. >> >>> > 2 - are we going to timebox the milestones, or plan on features added? >>> >>> personally i think we should come up with a list of all the features >>> we want, throw them into a backlog, and timebox it. >> See the wishlist: >> http://cwiki.apache.org/WICKET/wicket-14-wish-list.html >> >>> > 3 - how many milestones do we plan? >>> id like 6. 1-4 dev, 5-6 stabalizaton. we were never able to get away >>> with just one beta release before, most bugs are found after we put >>> out the first beta...so i dont expect a lot of bugs to be found >>> until the last dev milestone goes out. >> Fine with me. >> >>> > 4 - which features go into each milestone? >>> what are the features? :) >> :D >> >> http://cwiki.apache.org/WICKET/wicket-14-wish-list.html >> >> Martijn >> >> -- >> Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.1 >> is released Get it now: >> http://www.apache.org/dyn/closer.cgi/wicket/1.3.1 >> > > - -- Philip A. Chapman Desktop and Web Application Development: Java, .NET, PostgreSQL, MySQL, MSSQL Linux, Windows 2000, Windows XP -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFH2udTAdpynRSGw3URAiruAKCHqTPX+C5cmsxYqNTGHHX8SiADOwCeL5s0 vFUNXH0nPIfR1A/qOIknqkU= =dsVB -----END PGP SIGNATURE-----
