Re: Antwort: Wicket community traction / Wicket Web 2.0 experience
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 that is working in a sub-project with GWT and they chose it using that same argument: easy creation of Web2.0 style user interfaces. But now, they are going nuts because of how big the code is getting (and the project is by far from the end) - so, it's not just about few effort. You have to consider everything. Maintenance is one of them. By the way, it's really hard to create custom components within GWT. So I think you can see the problem here about code size. But, good luck for the rest of you team... I'll pray for them... :-D Best regards (really), Bruno On Oct 22, 2008 6:41am, [EMAIL PROTECTED] wrote: 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 -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Antwort: Re: Antwort: Wicket community traction / Wicket Web 2.0 experience
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 the best... Kind regards, Christoph
Re: Re: Antwort: Wicket community traction / Wicket Web 2.0 experience
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 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 the best... Kind regards, Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Antwort: Wicket community traction / Wicket Web 2.0 experience
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 argument: easy creation of Web2.0 style user interfaces. But now, they are going nuts because of how big the code is getting (and the project is by far from the end) - so, it's not just about few effort. You have to consider everything. Maintenance is one of them. By the way, it's really hard to create custom components within GWT. So I think you can see the problem here about code size. But, good luck for the rest of you team... I'll pray for them... :-D Best regards (really), Bruno On Oct 22, 2008 6:41am, [EMAIL PROTECTED] wrote: 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
