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. -- Ian Clarke Personal blog: http://blog.locut.us/ -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20120314/9a6ab9bf/attachment.html>
