Andrei, thanks for response. In our architecture we have a MainModule that manages all aspects from Layout visualization, e.g. to request for maximization in the central region, or to request for display another region in the general layout. Also defines common places that are used by other modules, e.g. ConfigurePlace, FindGloblaPlace. In that case, the main module reacts by setting the layout.
This MainModule define some handlers to response a request from the other modules (entry points) over localization in the Layout. Our MainModule registers all modules in the aplication, exists modules that are entry points and others that are inside distribution (same compilation). The MainModule in itself is an module. Your proposed solution is ok, but, the fact of reload pages for each link of module, disables the posibility to manage external Layout from a MainModule. We want to make each module to have their own stack of places, placehistorymapper, placecontroller and placehistoryhandler, event MainModule. El miércoles, 12 de septiembre de 2012 09:26:00 UTC-3, Andrei escribió: > > Christian, > > I should have a mentioned a more obvious solution too. > > Don't use PlaceController for the side menu. Make it a widget that > contains links to places in your modules. You can include this widget in > each module. When a menu item is clicked, the entire page reloads. This way > browser history will work as expected. > > Andrei > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/H2tnNNbg3jUJ. 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.
