> > 3) If we would ever backtrack on the constructor change (*if*, don't panic > > for now) how much trouble would that give you? > I don't believe that this would be a real problem. The task consists for > changig changing > > new Component(this > > into > > this.add(new Component > > in most cases. But I was convinced of the advantages that the new constructor > has and the question is now > 1. Are the proposed advantages no longer advantages
Yes, they still are, though improved header contributions make that you don't often need the path at construction time, but instead can use a model for that. Also, I'd like to state again that for simple things, I like the more compact style of 2.0. And I actually like the automatic re-parenting that some others dislike. But a big problem is that some of the more dynamic things got more work/ uglier to implement. > 2. Does the new constructor make anything impossible that was possible with > the old style contructor? Some things. My biggest disappointment was that wizard steps can no longer be panels as well, but have to work with a factory pattern. So at least that component got uglier in 2.0. > 3. What does the wicket 1.x users prevent to switch to the 2.0 style that > goes beyond a simple syntax change? I think the big dividing line is where you primarily used components in a pretty straightforward manner, or whether you created lots of advanced custom components. If the latter is the case, upgrading or downgrading can be quite a bit of work. I think it goes too far to state that it concerns a full rewrite, but for a large project this certainly may make for a day or two excluding testing. 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
