I'd agree with Chris too. Swing apps can really attack a different a class of problems ... a completely different solution space. And in that regard - I think Swing (and/or strict desktop GUI development) would be a beneficial understanding/perspective to have in your toolbelt. I find this conversation enlightening ... one of Wicket's big selling points is the similarities to Swing's programming model ;) Once you get started, you will probably feel right at home working natively in Swing.
-Luther On Mon, Jun 15, 2009 at 7:14 AM, Christopher L Merrill < ch...@webperformance.com> wrote: > nino martinez wael wrote: > >> The largest issue about going towards a desktop solution with java are >> that designing the ui really are a pain if you dont use something like >> mattise, it's even worse that hacking html.. I'll agree on the javaFX >> > > Granted, HTML frameworks have come a long way in the past 15 years, but > even with Wicket, building GUIs is still easier with a dedicated graphics > toolkit. Even SWT is better than HTML/CSS. I worked a lot with AWT/Swing > in the past and now SWT/JFace/Eclipse RCP. For anything more than trivial > GUIs, either one is easier than HTML. No matter how good Wicket and AJAX > get, you're still fighting the underlying design principal of HTML - it > was designed for rendering documents, not building GUIs. > > my 2c, > Chris > > > > -- > ------------------------------------------------------------------------ - > Chris Merrill | Web Performance, Inc. > ch...@webperformance.com | http://webperformance.com > 919-433-1762 | 919-845-7601 > > Website Load Testing and Stress Testing Software & Services > ------------------------------------------------------------------------ - > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
