Instead of using multiple modules you can also used a single module.
For your "views" you create an implementation for each role that your
application requires. For example:
CatalogView
CatalogViewAdminImpl
CatalogViewEnduserImpl
The you use deferred binding to pick the right implementatio
On Sep 3, 2:33 am, Riley wrote:
> Naturally, though I'd been looking for these answers for an hour
> before I posted here, I discovered that if I used the google plugin to
> create a new HTML page, it automatically configured whatever it needs
> to configure to support two separate HTML pages wi
No, but GWT recommended us to merge trivial modules into one TOP
module to make sure the loaded sequence. Undoubtedly, your way is
correct as well.
I have a project with the same logic, and for it, I created several
Layouts and swiched them on TOP module via commands from server-side
code that re
Naturally, though I'd been looking for these answers for an hour
before I posted here, I discovered that if I used the google plugin to
create a new HTML page, it automatically configured whatever it needs
to configure to support two separate HTML pages with different modules
& different entry poin
I'm making an application that will have two types of users, type A
and type B. Type A users need MUCH MORE functionality than type B
users - in fact, type B users will only be able to see a single
screen, while type A will see more than ten.
I don't want all of the stuff for type A users to be d
