Regarding better multi-module application support

[bg]

I've posted this as an issue
(http://code.google.com/p/google-web-toolkit/issues/detail?id=620) but
would also like some feedback regarding this. To embellish a bit on
what was stated in the issue, I believe the that using history tokens
and application states is an effective way differentiate between the
functions of a web app, but this is only effective to a point. Once a
code base starts growing I believe it is necessary to have at least
very basic multi-module support. GWT in its current state limits an
application to one module unless small hacks are introduced.
Deployment is also a bit more complicated. Please take a look at the
issue, and let me know what you think. Perhaps there is something I'm
just not getting?

I appreciate your time.

bg

[Bruce Johnson]

I really want to follow up on this, but I'm out sick today and can't do my reply justice in my current state of mind. Thank you for bringing this up because I think it's a great opportunity to talk about the idea of modules and what the right way is to support big apps.

-- Bruce

[bg]

Attempting to bring this discussion to life, although there appears to
be a lot on the GWT table at the moment.

On Jan 24, 3:55 pm, "Bruce Johnson" <b...@google.com> wrote:
> I really want to follow up on this, but I'm out sick today and can't do my
> reply justice in my current state of mind. Thank you for bringing this up
> because I think it's a great opportunity to talk about the idea of modules
> and what the right way is to support big apps.
>
> -- Bruce
>

[Bruce Johnson]

On 1/31/07, bg <bgou...@gmail.com> wrote:

Attempting to bring this discussion to life, although there appears to
be a lot on the GWT table at the moment.

Yeah, seems like we're kinda saturated right now. Wanna try again around the middle of next week?

[bg]

Yeah, I'll wait until things have have settled down a bit in regards
to other ongoing discussion.

On Jan 31, 11:39 am, "Bruce Johnson" <b...@google.com> wrote: