On 10/16/07, Neil B. Cohen <[EMAIL PROTECTED]> wrote: > I've been asked to look at possibly using the Google Web Toolkit instead > of (along with??) Wicket for my project. I don't know anything about > GWT, and I've only been looking at Wicket for about a week. Anyone care > to comment on the pros and cons of using these two? What makes one > better for a particular project than the other? Are they similar or > completely unrelated?
You can use them together, though you typically want to cut the number of technologies you use. Best thing you can do is play with both and see what you like best. I think that GWT works well if you want to develop your application as one or more 'applets', have a shallow domain model and a service oriented architecture, and you can go Ajax all the way. Wicket works well for a mixed model, when you want to have control over your URLs (e.g. for bookmarkability/ indexing by search engines) and use a rich domain model. Also, with Wicket, you directly control the HTML you use, whereas with GWT you work with layout managers. There's probably a lot more to say about this, but please play around and compare for yourself. Eelco --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
