Commentaires pour Appliweb http://blog.appliweb.net All dimensions of your web developments Mon, 22 Feb 2010 20:06:47 +0100 http://wordpress.org/?v=abc hourly 1 Commentaires sur JSF with a web designer par wpadmin http://blog.appliweb.net/2008/12/jsf-with-a-web-designer/comment-page-1/#comment-140 wpadmin Mon, 22 Feb 2010 20:06:47 +0000 http://blog.appliweb.net/?p=99#comment-140 I'm currently evaluating Wicket for Appliweb project. What a relief ! Simple stuff, cleanly designed. That sounds good. I’m currently evaluating Wicket for Appliweb project. What a relief ! Simple stuff, cleanly designed.
That sounds good.

]]> Commentaires sur JSF with a web designer par commonner http://blog.appliweb.net/2008/12/jsf-with-a-web-designer/comment-page-1/#comment-139 commonner Mon, 22 Feb 2010 07:05:26 +0000 http://blog.appliweb.net/?p=99#comment-139 I guess WICKET would have been a pretty good choice here, it's very flexible regarding the html, and you'd prolly just have integrated the designer's html & css as is, added a few wicket:id tags on key elements to add some logics, and that would be it. I guess WICKET would have been a pretty good choice here, it’s very flexible regarding the html, and you’d prolly just have integrated the designer’s html & css as is, added a few wicket:id tags on key elements to add some logics, and that would be it.

]]> Commentaires sur JSF with a web designer par kristian http://blog.appliweb.net/2008/12/jsf-with-a-web-designer/comment-page-1/#comment-135 kristian Sun, 21 Feb 2010 11:14:11 +0000 http://blog.appliweb.net/?p=99#comment-135 this has been our experience too; we finally switched to Tapestry this has been our experience too; we finally switched to Tapestry

]]> Commentaires sur Fragmented Java or no Java ? par John Smith http://blog.appliweb.net/2009/06/fragmented-java-or-no-java/comment-page-1/#comment-127 John Smith Tue, 16 Feb 2010 12:24:01 +0000 http://blog.appliweb.net/?p=73#comment-127 The good thing about your fragmented platform that is Java based is that it will not gain enough marketshare where it will matter that you need to test on all platforms. The low number of users on each device will mean that it won't be cost effective. The good thing about your fragmented platform that is Java based is that it will not gain enough marketshare where it will matter that you need to test on all platforms. The low number of users on each device will mean that it won’t be cost effective.

]]>