> > > going the other way 2.0->1.x should be trivial > > > > This is true. At least it should be a lot easier. > > I wouldn't be so confident. In 1.x very often we need to refrain > doing things in the constructor, and have to override onAttach() > to access the parent. So it's not just about reverting the > constructor change, it's also dealing with the delayed hierarchy > setup that 1.x forces you to cope with.
True. But the funny thing is it turns out we don't need to as often. Especially not since the HeaderContributer was refined. But indeed, YMMV. 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
