One more point: you can integrate your "monolithic" GWT app with the browser's native history support (including previous/next buttons and bookmarks) by using the History/HistoryListener GWT support. There are examples and tutorial in the docs page.
On 8/26/08, walden <[EMAIL PROTECTED]> wrote: > > > Sam, > > Len makes a good point: if you are building an integral application in > GWT, then you don't want to switch pages the way you do in a legacy > HTML application. You want to "stay resident" by switching out DOM > content. > > At some point, though, you will have another HTML page, and I think > the answer you are looking for with regard to reusing widgets > developed for page numero uno is this: > > a. to keep programming simple, your second page needs its own > EntryPoint and Module > b. your second Module can inherit your first Module, so you can reuse > its custom widgets > > So check the GWT docs for the section on Modules and inheritance of > same. > > Walden > > > On Aug 26, 5:04 am, Len <[EMAIL PROTECTED]> wrote: > > Hi > > > > Well you need to think about it differently - This is an application > > that runs in the browser and not a set of html pages. The rough idea > > with different html pages is that they would be different modules in > > GWT - each module is an application (or part thereof that operates > > independently) > > > > So in your case you want to have more than one panel in your application. > > > > Panel startPanel = ... > > Panel nextPanel = ... > > > > At the beiginning of the application in the entry point class you set > > the root panel to your fist panel > > > > RootPanel.get().add(startPanel); > > > > In your start panel there is a button > > > > Button nextButton = ... > > > > That is added to the startPanel > > > > startPanel.add(nextButton); > > > > The nextButton has a Listener attached to it that is called when the > > button is clicked. The listener then changes the panels > > > > RootPanel.get().clear(); > > RootPanel.get().add(nextPanel); > > > > Hope that helps > > Len > > > > > On 26/08/2008, Sam <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > Hi Len > > > Thanks for the prompt reply. I do admit that we can use panel. What my > > > concern is , if I render some widgets on lets say abc.html and it is > > > mapped to some java file which implements EntryPoint interface. This > > > abc.html file has a NEXT button on it . And this next button takes me > > > to lets say pqr.html. Now if I wanna render any widget or lets say a > > > pannel on which I added some widgets , do I need to write a class > > > which for pqr.html too which implements EntryPoint interface. > > > > > Thanks > > > > Samir- Hide quoted text - > > > > - Show quoted text - > > > > -- Renato Mangini http://www.linkedin.com/in/mangini --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
