I, personally, don't care for HTML, and perhaps I might enjoy programming in Echo2 better.
But suppose an employer maintained an HTML fragment with links to their entire portfolio of web applications, and wanted this fragment to appear on every page of each web application. Since someone else is maintaining that scrap and keeping it up-to-date, I would not want to translate it into Echo 2 and maintain my own copy. Would it not likely be easier to incorporate such an HTML scrap into a Wicket application, versus one written in a framework such as Echo 2 that abstracted away the HTML completely? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Eelco Hillenius Sent: Wednesday, May 17, 2006 10:58 AM To: wicket-user@lists.sourceforge.net Subject: Re: [Wicket-user] Google Web Toolkit integration ? > It's certainly an intriguing idea (have a look at haxe.org if you find > it interesting), ... ... Yeah. I see some advantages of using layout managers - basically the same promise as Swing has - but currently I would still prefer using HTML for layout. If I would like the GWT way of developing applications, I would have choosen Echo 2 a long time ago. GWT looks like a next gen Echo to me, though with a very big name behind it, and some cool innovations. ... Eelco ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642 _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
