On Tue, Sep 18, 2012 at 3:30 AM, Ray Cromwell <[email protected]>wrote:
> I favor splitting things up into reasonable chunks that have > coherence. e.g. Logging, RPC, RequestFactory, Editors, UI Widgets, > ClientBundle, Core, Events, Dom, etc. > > For example, I should be able to get away with consuming Core + > Logging (in reality, I probably can't because of the Widget based > debug panel), or Core + Logging + Dom + Events (pure DOM based app, > no Widget framework, no RPC, etc) > > One reason for doing this is faster builds. The fewer classpath > entries, the better. Secondly, I think it gives people a better idea > of what you're using. IMHO, inheriting User.gwt.xml is the GWT > equivalent of "import com.google.gwt.user.client.ui.*", it's a star > import. > > We can still have a uberjar gwt-user module, but other people can > start have fewer dependencies if they want. Plus, when hacking on GWT > itself, if I modify say, ClientBundle, I don't end up rebuilding > everything if my app doesn't depend on it. The only caveat there is if you break it up into smaller chunks you can't have circular dependencies between the chunks. I think that means that some things will have to get promoted to core that otherwise wouldn't, unless some effort is made at refactoring things (which might be a breaking change). -- John A. Tamplin -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
