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.
However I love Wicket for its simple separation of UI/Control/Data it
makes it easier to develop an application rapidly, particularly if you
have to pass the UI development to another person (very difficult to
do in GWT unless that the design guy is comfortable compiling code,
which most are not).
I have attempted to integrate the two with some success, although in
what I was doing, once GWT was loaded and running, wicket had very
little do do any more (mostly page security and file upload tasks). I
have some idea on how you could use them together making client side
components in GWT that could be used in Wicket, but I have not had the
time to actually sit down and experiment.
The short version of the idea is that GWT has the ability to bind to
arbitrary elements in the page its sitting on, and you can pass data
back and forth... so my idea is to make your interactive components in
GWT, compile them, and write a wicket component that could make sure
all the GWT setup was done.
This would allow you to do client-side interactive components. doing
ajax calls with it would be more problematic, but still possible as
GWT does support other forms of remote calls than its built in protocol.
If such an integration is possible and works cleanly, it will be far
superior to YUI, but the components would be static (they have a
specific function and thats it, similar to YUI). Forget about
dynamically building GWT components within wicket. although I think it
might be possible, I think it would be pretty hacky and not worth your
time.
- Brill Pappin
On 8-Apr-09, at 9: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 characteristics as Wicket (focus on
code, not
markup) with the major difference/benefit as I see, that is does not
maintain any state on the server. Also, with GWT you seem to get more
readily available components (i.e. http://extjs.com/explorer/). The
bennefit
of Wicket as I can see, is that applications potentially degrade
nicer and
the programming model hides the Ajax RPC better. Any thoughts?
/Casper
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
