You might want to look at this article:
http://claudiushauptmann.com/a-framework-for-gwt-multipage-applications.html
On Nov 16, 5:36 am, Davis Ford davisf...@zenoconsulting.biz wrote:
I'm doing this now. I set the project up this way several months ago and it
works great for me. The only real
I'm doing this now. I set the project up this way several months ago and it
works great for me. The only real con is double compile-time, but I don't
care about that. I even have a feature where I can show a view of one
application inside another, which is very cool.
Here's how I set it up --
Thanks for the replies, guys, and yes that's a great explanation! We're
very new to GWT. So, clearly we're learning these ins and outs.
Unfortunately, we started with a Struts2-based application, and we're
only adding new screens in GWT as they come up. I'll have to think
about it, but it's
What's the best way to create a web app with multiple entry points but
a lot of common code (eg. common widgets and dialogs) shared between
them, as well as a common server back end? Currently I'm creating
multiple modules and multiple HTML pages within a single web app but
I'm also worried about
I guess I should probably have a single module and top level entry
point and then switch between interfaces from there but that will
involve a lot of code refactoring.
It doesn't need a lot of refactoring, it can be done on an incremental
basis.
I am assuming have 3 entry point classes
Multiple modules is the wrong way to use GWT.
GWT highly recommends using a single module. Most of the performance
optimizations GWT does relies on the fact that you have a single, monolithic
module. Plus, as you observed, the time to build your application keeps
growing as you add more modules,
Great explanation Sri, I just wanted to add that you could also do
both.
In my project, I have two GWT entry points (and about 5 GWT modules
for sharing / reuse), but I also have another 4-5 regular web pages
with static content.
You need to decide the portions of your site that require the
Specifically, I'm curious about the use of GWT Modules in a project.
Each time we have a new screen to create, we have been adding a new
module to our project. Of course, with each new module, there is an
additional build cycle to generate the Javascript for that module. What
I'm wondering is