Isaac beat me to the punch, but we've had the same experience here. All of our apps are inside the firewall, and therefore search indexing and no-javascript are not concerns. Any hardcore AJAX app, GWT or otherwise, has the same two concerns outside the firewall.
Having said that, I feel that you have about the same flexibility in either of your scenarios. But you'll probably find that the maintainability will be greater if you use one sparse HTML page, especially if you are using an IDE like Eclipse or NetBeans. On Oct 31, 11:17 am, "Isaac Truett" <[EMAIL PROTECTED]> wrote: > I do the entire UI in GWT and CSS on one fairly sparse HTML page. Two > things that might make me change my ways would be needing to be > indexed by search engines or needing to be accessible by browsers > without JavaScript. None of GWT apps so far have had either of those > requirements. > > > > On Fri, Oct 31, 2008 at 7:03 AM, Alex Reid <[EMAIL PROTECTED]> wrote: > > > Hi, > > > I was wondering what approaches people took with regard to host pages. > > > Is it better to let GWT manage the whole page, perhaps with a single > > root DeckPanel ... OR is it more flexible to setup the majority of the > > application layout using standard HTML/CSS, slotting Widgets instances > > into these divs later on? > > > I can see merit in both approaches. > > > Alex- Hide quoted text - > > - Show quoted text - --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
