Thanks for all the info. I've been in the Swing world for 10 years and need to come up to speed on the alphabet soup of the Web World in a few scant weeks ;-) My knowledge of Ajax is, shall we say, a bit sparse...
Wicket and GWT seem to be the most swing-like, and they are both easy to become productive on in an hour (or less). It does boil down to "the right tool for the right job", and management is looking for the framework of "the future", even though we have no idea what we are supposed to be building... We spent a couple weeks writing prototypes using 5 different frameworks, then evaluating each one; GWT came out on top with Wicket a close second. Tapestry was low, but it got pulled forward anyway since it was Tapestry ;-) I still have some code our architect has put together to accomplish a "non-trivial" task and he is not happy with the amount of code he had to write to accomplish the task. I need to find a way, if possible, to simplify it. Thanks again for all of your input, rhogue ------------------------------------------------------------------------- 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
