> I have been using 1.2.4 for some days. I think the current construct works > well. If there is no overwhelming reason, I prefer preserve the old style. > Why wicket team choose SWT style construct for 2.0? To prevent mistakes like > forgetting to add component to component tree?
The reasons are outlined here http://cwiki.apache.org/WICKET/migrate-20.html#Migrate-2.0-Constructorchange. Mainly line precise early error reporting when the component hierarchy mismatches with the hierarchy in the markup, and to enable users to do a couple of things at construction time they now have to do workarounds for (like doing getForm() or getMarkupId in the constructor). 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 Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
