There is no real easy way, but to do it :)
I find the hardest thing about Wicket, particularly when your first
starting out, is discarding all the old ideas about how a webapp is
built...
Having worked in the field for a long time, servlets, JSPs, Struts,
etc. it took me a while to get over the old patterns of doing things
and start thinking more wicket'y
I still have trouble with WIcket now and then because there *is* quite
a lot of complexity when your doing something non-standard, however I
usually find that the answer is the obvious one and trying something
usually works... and when I think about it, i realize that the same
non-standard "thing" i was doing would have taken just as much time in
any other framework to sort out.
What I love wicket for in particular, is the very good separation
between view and controller/model. no more crap logic in my HTML!
Yay.
Anyway, i'll continue to use both GWT and Wicket.
- Brill Pappin
On 8-Apr-09, at 9:24 PM, ying rss wrote:
I played with both GWT and wicket. I was drawn to wicket by several
reviews
and I'm disappointed.
I use maven to build gwt and ext-js and GXT which works very well.
Compilation is slow but with tuning to specific browser, the call
stack is
straight forward. It's my feeling that GWT is closer to core java than
wicket.
* I don't know much about javascript so I like the idea of language
separation in GWT. Not very much into wicket's way to blend everything
together.
* Appreciate the fact there are samples for wicket. But Wicket's
documentation and samples are not enough. There is a lot of pain to
do a
little bit more advanced things in wicket for beginners and there
are many
user requests in user email list. I never had so much trouble in my
gwt
project. Maybe I haven't found a easy way out. Appreciate any
suggestions.
--
View this message in context:
http://www.nabble.com/GWT-vs.-Wicket--tp22950178p22962926.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
