Hi,
I like what I see with the improvements of 1.6! I am building a
enterprise application at a major telecom company which is getting
used, in which I am fully utilizing gwt. I also have built
GoneVertical.com application.
This is a great question. I have been experimenting with including my
modules like this. Although I haven't had all the items come together
like I want I have gotten close. I haven't been able to build included
projects with my current war builder. I really like the new system,
but haven't got Ant figured out to include other modules, and then get
the other module classes included into the war.
This is my goal for my project builds. I have successfully testing
including modules in 1.6 like this, but building them I have not.
> Navigational Core Module - entry point resides here, directs the applications
> rendering
> Login Module - login widgets and class
> Common Module - common widgets and classes
> Options for more included modules
> Project Module - current working project
I am a GWT promoter!
Brandon
On Mar 20, 6:47 pm, Lance Weber <[email protected]> wrote:
> With the arrival of the new project structure in 1.6 I'm looking for
> recommendations/experiences on organizing complex applications
> containing several major functional areas.
>
> For purposes of this discussion, I'm envisioning
> -Application A
> --Functional Area A1
> --Functional Area A2
> --Functional Area A3
>
> Assuming each functional area shares > 50% common entities, business
> logic and gui components, it isn't clear to me what approaches to
> organizing the codebase will scale with the eventual size of the
> application. Here are some of the options as I understand them:
>
> 1) Monolith Option. One project with one module, possibly supporting
> multple entry points.
>
> 2) One project, multiple modules. Maintain one project, but create
> multiple modules to organize common classes and functional areas. (How
> do you accomplish this in 1.6? It's not clear to me)
>
> 3) Multiple projects, one module per project. Create one project for
> each module, resulting in a commons project and a project for each
> functional area.
>
> Any thoughts/comments on this would be welcome...
> Advantages/Disadvantages?
> Options I'm missing?
> Good/Bad experiences with these approaches?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
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
-~----------~----~----~----~------~----~------~--~---
