GWT MultiModule

Options

  1. Use different HTML files for the various pages and then also provide this pair for the entry point (called {ep} below)
    1. {ep}.gwt.xml
    2. {ep}.java (implementing the onModuleLoad() method)
    3. {ep}.html (holding the .noCache.js file in the appropriate <div>)
  2. Load it all at once and give hide/view capability similar to the ListTags where I had a second column (or not) based on whether the user was logged in or not.
  3. Use a GWT Library to pull together common client code.
  4. Still looking for a good "server side" solution that isn't tied so closely to the service generation.

In both cases, there is a single .war file that is generated, but different "entry points" and thus potentially different looks. Using OpenID, it is possible to restrict users to certain "entry points".

Examples under consideration

single app; multi-window

  • Page with optional hide/view capability for an info panel in the corner
  • Edit routes app for pulling together pieces into larger wholes (GPX Edit)
  • Ability to 'checkbox' in/out overlays such as water fountains, hills, facilities

Separate entry point; shared libraries within the app

  • Manage the DisplayGroups page (including capturing BikeTrains)

Both multi-window and separate entry point

  • Creating Overlay files automatically based on a selection of routes to be grouped into a 'tag'

References

  • There is the issue of loading multiple pages — each containing a substantial set of library code — versus a single large page that holds more.
  • A separate app altogether may be OK, but does it compile into the same executable with a separate entry point?
  • Some discussion about optimizing, leads to an example of separating out the core from the pages.
  • multi apps within same folder - undecided if this is helpful or not.
gwt
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License