Yes, you are right Dan, comparing GWT and Wicket is like comparing apples and oranges.
In theory you can have complete website using GWT, but here are the pitfalls: 1. With GWT your site will not be indexed in search engines because you have only one page for the whole website and the contents will not be visible to search engines. 2. Back Button Issue - Even though GWT has the tokens which can tell application about it's state, but they are not yet ready for the prime time, their behavior is just too erratic specially in IE because IE will download the whole application again and again for each back button click and IE stores only a few token in the browser history. The easiest way to get best of both worlds is to create one RPC service to provide data to GWT apps, then just embed the GWT apps on any page in the Wicket you like, it's fairly simple. -Jay Dan Kaplan-3 wrote: > > I've scoured the internet to figure out how to integrate a GWT app inside > a > Wicket App. I'm not getting very good results. I also checked the > mailing > archives and didn't really find any technical advice on how to do this. > > > > First, I noticed a lot of the attitude towards GWT/Wicket is that you > usually want to choose one or the other. I disagree. In fact, I think > comparing GWT to Wicket is comparing apples and oranges. GWT is a > Toolkit, > and Wicket is a Framework. They both do different things and they're both > very good at what they do. Therefore, it's worthwhile to have GWT > integration in wicket. > > > > The reason I personally want GWT support is because I'm making a game. > It's > mostly a traditional webapp, but I also want to have an AJAX app that > works > similar to Google Maps that allows users to visualize the world. Most of > my > website will be Wicket, but from what I've seen of Wicket's AJAX support, > making this Map app would be much easier to do in GWT (no offense). > > > > That being said, I've also inferred from most of the Wicket + GWT > conversations that the Wicket developers are trying to add some huge > functionality to Wicket to allow you to place the a GWT app from your > WebPage classes. That may come in handy, but I'm not so sure that it's > necessary. I think the client side code that GWT requires could easily be > added by hardcoding it in the markup and that would be good enough for > most > (myself included). The part that's tricky to me is this section: > http://code.google.com/webtoolkit/documentation/com.google.gwt.doc.Developer > Guide.RemoteProcedureCalls.html > > > > Specifically, if you scroll down a little to the image, how do you get the > right side to integrate with Wicket? As you can see, GWT uses a > RemoteServiceServlet if you want your GWT app to communicate with the > server. But the wicket philosophy seems like it tries to hide Servlets > from > the user. So, in short, can anyone advise me on how to integrate a GWT > app > with Wicket? > > > > Thanks, > > Dan > > > -- View this message in context: http://www.nabble.com/GWT-%2B-Wicket-tp14284738p14355045.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
