Currently, I'm rewriting our GWT-based application and I picked Wicket.
GWT is delicious but only on papers.
GWT cons:
1. lack of roles separation, building the GUI in the code doesn't work for
me.
2. Hibernate integration is a nightmare.
3. Unit testing isn't that agile thing.
I like GWT but I wo
Casper, for the case when you can not enforce your users to have
javascript, it's more worthwhile to compare Wicket to Tapestry5.
I'm evaluating the latter right now.
On Wed, Apr 8, 2009 at 4:11 PM, Casper Bang wrote:
> I was just wondering about the Wicket community's opinion of GWT. It seems
>
I really like the idea behind GWT. And striving for a statically typed
'true' OO programming model is what GWT and Wicket have in common.
I haven't build anything with GWT, so my opinions in this respect are
what I infer from how I think GWT works. I expect GWT to scale more
easily if you plan wel
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
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 c
There was a grails-wicket plugin but I don't think it works with any recent
version. They are also working on making grails more modular with standalone
GORM etc...
Also heard somewhere that Groovy 1.7 or 1.8 will allow anonymous inner
classes.
On Wed, Apr 8, 2009 at 8:53 PM, Andre Prasetya wrote
Thank you for your mail. I am presently on vacation and will return April 14th.
If you need urgent assistance, please email supp...@bookingbooster.com. You can
also reach our Support via Skype callto://premiersupport
Thank you
Best regards,
Nick Wheeler
Booking Booster.com
t: +44 (0)1273
Zk ia good for buildng qpplication bt the zul wndow layout is just
like that. And the license os stopping us from buildng commercial apps
wthout buying their licnse.it worth th money but if u live in an
economically poor country,you can't afford it.
I wish wicket can play nicely with grails,having
Getting to to do something specific is not usually my problem with GWT
(its component model feels just like Wickets does)... the biggest
problem I have is having less control over the html, which makes
things a bit harder to deal with (Googles ui style now is partly the
result of how you wo
Thank you for your mail. I am presently on vacation and will return April 14th.
If you need urgent assistance, please email supp...@bookingbooster.com. You can
also reach our Support via Skype callto://premiersupport
Thank you
Best regards,
Nick Wheeler
Booking Booster.com
t: +44 (0)1273
> P.S. people say my article is "one sided" but no-one can explain *why ;) -
> ok, ok this has been discussed to death in the comments there ...
>
I should mention I love wicket (coming from JSF) but has only limited
exposure to it while having no experience at all with GWT. However while
readin
I thought Matt Raible had some success with getting GWT to play nice with
Maven:
http://raibledesigns.com/rd/entry/modularizing_gwt_applications_with_gwt
Personally I would choose GWT only when I want to keep server calls to a
bare minimum. "Ready made" components and all may look enticing, but
Yah, its a pitty, but the Google guys are pretty down on Maven.
I once asked them to look into making it more maven friendly, and got
throughly blasted.
if I remember correctly the comment from one of the GWT developers was
something along the lines of "we don't want to waste our time with
I've used both extensively now.
I think the comparison is an apples <-> oranges thing however.
GWT does not really play well with other frameworks because of its
generated code, but if your doing a mostly client side/ajaxy
application, nothing beats it for performance and maintainability.
Hi,
You may also take a look at ZK framework. It's also a kind of framework
which can be used to build beautiful RIA's. You can chose to use it by
writing your app in just Java or in Java/Zul.
http://www.zkoss.org
But in my opinion, Wicket stills beter then these kind of frameworks :)
Regards,
> Peter Thomas did a great side by side you should checkout:
Good article, if perhaps a bit one-sided. I can understand how
separation-of-concerns/composability comes slightly more natural to Wicket.
However the performance, flexibility and component repertoire of GWT along
with steadily more capa
Working with GWT is kind of a nightmare. You have to write custom build
scripts for any library / module you use so that the sources are included in
the jar and available to the GWT compiler. Until GWT has a build system that
is better I'll stay away from it. Really a shame because the programming
Peter Thomas did a great side by side you should checkout:
http://ptrthomas.wordpress.com/2008/09/04/wicket-and-gwt-compared-with-code/
Craig.
On 8-Apr-09, at 8:11 AM, Casper Bang wrote:
I was just wondering about the Wicket community's opinion of GWT. It
seems
to share many of the positive c
18 matches
Mail list logo
