On Wed, Oct 1, 2008 at 1:09 AM, bill robertson <[EMAIL PROTECTED]> wrote: > I'm aware of the concept, but I still am of the opinion that if you > use GWT "all the way" it is mutually exclusive of that approach. > > I am also aware of the new DOM apis, and somehow that makes the > "unobtrusive javascript" way of doing things somehow possible in GWT, > but that's not really how I think GWT is best used. I like the uber > fast nature doing an RPC hit and only updating the parts of the page > that change, but what I don't see is how to make that search friendly. > > Step up to the plate Google.
I think either you've misunderstood "hijax", you've misunderstood GWT, or you're being belligerent. GWT is not an all-or-nothing tool, so I think it's unfair to demand that anyone make it trivial to use _all_ of GWT in an search-engine-friendly way. If you want a page that's search-engine-friendly, you need to make a page that's search-engine-friendly--it's as "simple" as that. If you use GWT in such a way that you're constructing all your widgets out of thin air with the new operator, then you're not making a page that's search-engine-friendly because you're relying on Javascript to create your content on-the-fly by manipulating the DOM. I'm reasonably sure it's provably impossible for Google or any other search engine to automatically index all of a 100%-dynamic page. (Simulating an algorithm is, AFAIK, isomorphic to executing it and a typical Javascript app effectively has an infinite number of inputs because any given event _could_ do something significant.) Anyway, my point is, you have to choose and it's up to you to design your page in a way that meets your requirements. The guy that coined the term hijax suggests designing for AJAX first and implementing AJAX last. If your app works without AJAX, there's a good chance it's search-engine-friendly. If your app already works, you should, in theory, be able to enliven it with judicious uses of GWT. GWT has all the tools necessary to do that (AFAIK) and I think the lack of any such tool would be considered a bug. Ian --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
