Hello Everyone, normally GWT apps are consisted of only one HTML page. this html page loads one or more scripts. User navigation is through manipulating the history tokens/Places.
what if someone decided to implement the approach below: instead of having only one HTML page for entire application, have one HTML page per functional area (workspace/section). for example, if an application has Employee Management section , Document Management section, AccountSettings section, Message/Notification section, what if, these four different part of the application, were in fact in four separate HTML files. and navigating from one section to other, was done in traditional sense. each section, in its own page, showing widgets/interacting with user, loading data/ etc .... basically an independent application on its own and once user decides to navigate away to different part of an application, it is basically a different gwt .html page. to summarize, partitioning our big application into semi-autonomous sections, with their own .html file. and linking these sections through "<a href=" "> after all, these gwt main html files, are basically empty, just loading a script, so it is not like we are loading a heavyweight html page. what is wrong with this design ? what are the implications ? -- 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.
