Hehe Bruno
I were about to write a similar mail..
[EMAIL PROTECTED] wrote:
That's ok Chris,
It's just a matter of time until they find out they did the wrong
choice - unless this is going to be a small software, with very
specific functions, like GMail. :-) There's a team by my side here
Hi Bruno,
I appreciate it that you pray for the rest of my team :-) I won't be a bad
looser, so I will give my best with the other devs to build a good
solution with GWT. I really hope that it is not inherent to GWT that the
code gets big and unmaintainable. So I cross my fingers and hope for
http://ptrthomas.wordpress.com/2008/09/04/wicket-and-gwt-compared-with-code/
-igor
On Wed, Oct 22, 2008 at 10:42 PM, [EMAIL PROTECTED] wrote:
Hi Bruno,
I appreciate it that you pray for the rest of my team :-) I won't be a bad
looser, so I will give my best with the other devs to build a
Martin, Richard, thanks for your answers!
Unfortunately, I could not convince the other devs of the various
advantages of wicket. The team chose GWT because it allows to create Web
2.0 style user interfaces with fewer effort.
Regards,
Christoph
That's ok Chris,
It's just a matter of time until they find out they did the wrong choice -
unless this is going to be a small software, with very specific functions,
like GMail. :-) There's a team by my side here that is working in a
sub-project with GWT and they chose it using that same
Hi Wicket users!
At my company, we are currently evaluating technology choices for building
web user interfaces. We narrowed our candidate list down to two remaining
candidates: Wicket and GWT. We already did some prototyping with these
two. Our main conclusions are
- Wicket has the better
We have just started evaluating frameworks to migrate our Struts 1.x apps.
We are considering Wicket, GWT, and Spring MVC (I know, they are quite a bit
different). Having prototyped in Wicket and GWT, which do you think allows
you to write code that is easier to maintain?
There is a wiki page
just some quick pros for wicket which helped us to make a decision
(someone please correct me if i'm wrong on any of these):
* wicket started from a professional background, ie people noticed
there is a reason to develop it because no available framework met
their needs
* the architecture is
