Comments on: Wicket API nicer than Swing? http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/ Ramblings on Java, Wicket, cats and other stuff Mon, 05 Dec 2011 20:15:59 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Martijn Dashorst http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/comment-page-1/#comment-35674 Martijn Dashorst Tue, 05 Feb 2008 15:24:45 +0000 http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/#comment-35674 Yes I believe you when you claim it is incredibly more simple than Wicket. That is why I use Wicket, because it solves my problems with state management, back button support, Ajax components, creating reusable components, fine-grained component level security, large community, scripting less templates (i.e. *NO* Velocity which is a BIG plus), and more. If you can't manage inner classes, then yes, probably Click clicks with you. Yes I believe you when you claim it is incredibly more simple than Wicket. That is why I use Wicket, because it solves my problems with state management, back button support, Ajax components, creating reusable components, fine-grained component level security, large community, scripting less templates (i.e. *NO* Velocity which is a BIG plus), and more.

If you can’t manage inner classes, then yes, probably Click clicks with you.

]]> By: John Sorat http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/comment-page-1/#comment-35671 John Sorat Tue, 05 Feb 2008 15:11:43 +0000 http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/#comment-35671 Have you tried Click? http://click.sourceforge.net/ It's incredibly simple than Wicket... no nested inner classes... Uses Velocity for the 'view'... Have you tried Click?
http://click.sourceforge.net/

It’s incredibly simple than Wicket… no nested inner classes… Uses Velocity for the ‘view’…

]]> By: Ryan Sonnek http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/comment-page-1/#comment-26257 Ryan Sonnek Mon, 17 Dec 2007 00:57:57 +0000 http://martijndashorst.com/blog/2007/12/16/wicket-api-nicer-than-swing/#comment-26257 Thanks for the reference Martijn. What I think is particularly compelling about developing with Wicket is the true "separation of concerns". It's the "holy grail" of *any* development framework or API. Keep presentation and logic/behavior separate. HTML and CSS have come to rule the presentation layer, and Wicket does an *amazing* job of keeping logic out of the view layer. unlike some other frameworks *cough* JSP *cough*... If Swing (or some other framework) could get rid of Java for layout/presentation, and use Java for what it was intended for, behavior and logic, we'd be one step closer to great client side development API's. Thanks for the reference Martijn. What I think is particularly compelling about developing with Wicket is the true “separation of concerns”. It’s the “holy grail” of *any* development framework or API. Keep presentation and logic/behavior separate.

HTML and CSS have come to rule the presentation layer, and Wicket does an *amazing* job of keeping logic out of the view layer. unlike some other frameworks *cough* JSP *cough*…

If Swing (or some other framework) could get rid of Java for layout/presentation, and use Java for what it was intended for, behavior and logic, we’d be one step closer to great client side development API’s.

]]>