On Wed, Mar 14, 2012 at 06:03:25AM -0500, Ian Clarke wrote: > On Wed, Mar 14, 2012 at 5:17 AM, Nicolas Hernandez < > nicolas.hernandez at aleph-networks.com> wrote: > > > I have send en email about that. I can fill the decision matrix for you if > > you really needs. > > - Minimalist ui tools > > - poor production capacity in iterative mode, > > - developpers knowledge of Wicket, > > - capacity of using multiple UI with and without js (Lnyx, Web 2.0, > > Android, ...) > > > > are unfavorable compare to GWT > > > > These justifications seem pragmatic. I do agree that the development cycle > with Wicket can be a bit slow, at least 4 years ago when I last used it. > > Also, you are correct not to underestimate the importance of using a > familiar tool, it can make a huge difference in development time. > > Ian. >
They might be pragmatic but they miss the point. We want to change the templating engine so that 'web-designers' can use their favourite wysiwyg editor to help us come up with a kick-ass design. Code-maintainability and other software-engineering concerns are only secondary here... GWT doesn't allow that... The only wysiwyg editors I know about are within IDEs (Eclipse and Netbeans)... That's not the tool of choice of designers. You're still writing JAVA code as opposed to plain HTML. As far as I know, from the list of suggested frameworks, only Wicket fulfills this requirement. see: https://wicket.apache.org/learn/examples/helloworld.html Florent
