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 work with GWT).
GWT itself is pretty extensible, but I found that ExtJS was just the
opposite... although it has gotten better in ExtGwt.
Anyway, I actually like them both :) and keep both in my toolkit...
only wish they could play better together.
BTW - your article mentioned not being able to see the HTML... the
developer tools plugin for Firefox has a "View Generated Source"
command, which makes things a lot easier when your debugging GWT html
(I've even used it on Wicket for that matter).
- Brill Pappin
On 8-Apr-09, at 12:32 PM, Peter Thomas wrote:
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 in my
experience you always fall into the trap where they do *almost* what
you
want but not *exactly* (just like JSF).
In theory nothing stops somone from writing components as "rich
looking" as
ExtJS. I think Matej's "inmethod grid" is a good example.
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 ...
On Wed, Apr 8, 2009 at 10:00 AM, Brill Pappin <br...@pappin.ca> wrote:
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
garbage
like maven".
I didn't bother to argue about it, because if you know maven and
like it,
you know why its advantageous, and if your that set against it it
won't
matter what others say.
However there are a few maven plugins for it, and combined with the
war
overlay feature, it not to hard to get it all working and integrate
with
other projects.
- Brill Pappin
On 8-Apr-09, at 10:46 AM, Casper Bang wrote:
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 capable browsers leaves me with a feeling that
"I'll
get
more bang for my buck".
Until GWT has a build system that is better I'll stay away from it.
Since version 1.6 today, it uses normal Ant scripts (which I
suppose is
easy
to mavenize).
Thanks guys,
/Casper
---------------------------------------------------------------------
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
