Hi Paul van Hoven, As doopa mentioned, there are already a number of threads on the group talking about the crawlability problem for Ajax applications. There's one really great thread that sprang to mind that I suggest you check out. The problem is described in great detail and Ian gives an excellent explanation of the technique he uses to make his GWT application indexable by search engine.
GWT crawlability: http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/8fe6a3d2eaab80bb/ There is also another technique which you might want to investigate called "Hijax". You can read about it in the blog post below. A spider's view of Web 2.0: http://googlewebmastercentral.blogspot.com/2007/11/spiders-view-of-web-20.html The solution might not be as simple as you would have liked, but search engine crawlability for Ajax applications is indeed a complicated problem, so one would expect the solution to be at least somewhat complex, at least until other advancements in technology are made. For your earlier point about the speed of loading an app - firstly, I'm glad that performance is on your mind as you design your GWT application :-) Whether you use a single HTML file / structure or not isn't key to making a faster application, but rather a small part of it. The things that are most important to consider are the type of widgets you're using, how you're using them, the amount of rendering you're making the browser perform at a given time, the number of resources your users must download to run your application, and so on... GWT does a lot to optimize on all these fronts to make your application high performance, but you do have to be careful about how you design your application. That said, using a single HTML file is probably a good thing since it keeps the number of downloads required to load your application down to one file, plus any other image or CSS resources your application might require. Hope that helps, -Sumit Chandel On Thu, Mar 5, 2009 at 10:52 AM, Paul van Hoven < [email protected]> wrote: > > I'm writing a web app. The web app is fully written in GWT, no other > technology is used. Currently i'm having just one html page the > index.html. It looks like this: > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> > > <html> > <head> > <meta http-equiv="content-type" content="text/html; > charset=UTF-8"> > <title>Index</title> > <script type="text/javascript" language="javascript" > src="myProject.Index.nocache.js"></script> > </head> > > <body> > > <iframe src="javascript:''" id="__gwt_historyFrame" tabIndex='-1' > style="position:absolute;width:0;height:0;border:0"></iframe> > > <div id="screen" > > <div id="site" > > </div> > </div> > > </body> > </html> > > > I'm having a question about the design of gwt web app. > 1) Suffices it to have only one Index.html, or should there be other > pages like for example fotos.html or guestbook.html instead of > FotosWidget.java or GuestbookWidget.java? > 2) What about the speed of loading the web app, when using a single > html page structure? > 3) What about search engines? Is this structure okay for search > engines? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
