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]
Antwort: Wicket community traction / Wicket Web 2.0 experience
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
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
Wicket community traction / Wicket Web 2.0 experience
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 architecture (by far). - GWT allows to create Web 2.0 style user interfaces with fewer effort. I like Wicket because of the first argument. In our team, there are some objections against Wicket because of the second point and because some developers in the team think, that Wicket has not enough community traction and that no serious Web 2.0 _application_ uses Wicket. Can you help me to invalidate these objections and to convince my team of Wicket? - Which Wicket success stories do you know of? - Are there examples for serious Wicket applications? - How can I prove that there is community traction for Wicket? - Are there examples of a GWT style Wicket usage, that means lot of Web 2.0 user interface features realized with Wicket? Regards, Christoph
Re: Wicket community traction / Wicket Web 2.0 experience
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 with sites using Wicket: http://cwiki.apache.org/WICKET/sites-using-wicket.html Also, the Wicket in Action forward by Jonathan Locke mentions that IBM, TomTom, Nikon, VeriSign, Amazon, and SAS use Wicket. Thanks, Richard Allen On Tue, Oct 21, 2008 at 11:49 AM, [EMAIL PROTECTED] wrote: 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 architecture (by far). - GWT allows to create Web 2.0 style user interfaces with fewer effort. I like Wicket because of the first argument. In our team, there are some objections against Wicket because of the second point and because some developers in the team think, that Wicket has not enough community traction and that no serious Web 2.0 _application_ uses Wicket. Can you help me to invalidate these objections and to convince my team of Wicket? - Which Wicket success stories do you know of? - Are there examples for serious Wicket applications? - How can I prove that there is community traction for Wicket? - Are there examples of a GWT style Wicket usage, that means lot of Web 2.0 user interface features realized with Wicket? Regards, Christoph
Re: Wicket community traction / Wicket Web 2.0 experience
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 indeed better than anything i've seen in the java web framework world for a long time, core and pure oo concepts done right, and every dependency to a third party technology in wicket core is seriously debated and only implemented if there really is need for it. * wicket has a lot of traction, it's just not as loud as GWT's, which is quite understandable if you remind yourself what the G in GWT stands for * serious wicket applications: Dertour.de and connected domains...a rather serious application, because of 2 things: load and transactions. It's easy to build a shiny web2.0 thingy with nearly every technology out there, but the real measurements are scalability (load) and reliability (number and consistency of transactions). in the end it boils down to the numbers, and wicket will help you keeping them down, as it integrates very well with the whole JEE world, be it spring, jpa, hibernate, ejb or whatnot. if used right (which, btw, should be a disclaimer for all arguments regarding any framework), it eases code maintenance and narrows the gap between prototyping and production. but whatever you decide, trust your gut as an architect. regards, martin 2008/10/21 [EMAIL PROTECTED]: 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 architecture (by far). - GWT allows to create Web 2.0 style user interfaces with fewer effort. I like Wicket because of the first argument. In our team, there are some objections against Wicket because of the second point and because some developers in the team think, that Wicket has not enough community traction and that no serious Web 2.0 _application_ uses Wicket. Can you help me to invalidate these objections and to convince my team of Wicket? - Which Wicket success stories do you know of? - Are there examples for serious Wicket applications? - How can I prove that there is community traction for Wicket? - Are there examples of a GWT style Wicket usage, that means lot of Web 2.0 user interface features realized with Wicket? Regards, Christoph - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
