Yes, it's true, we spaced that EventBus is part of GWT's public API. We're now thinking that the new packages will be:
com.google.bindery.event com.google.bindery.autobean com.google.bindery.requestfactory Patches should start appearing this week. Note that this is strictly a refactoring of code that is already JRE compatible. The i18n subthread is interesting, but out of scope for this effort. On Fri, Mar 25, 2011 at 2:53 PM, Stephen Haberman < [email protected]> wrote: > > > Reactions? > > Having to change import statements sounds perfectly fine to me. > > Other misc comments from the peanut gallery, though likely nothing > you guys haven't likely already figured out. Just curious. > > Should c.g.requestfactory have zero GWT dependencies? I.e. this > non-GWT/pure JRE jar you spoke of would be everything in that package > (without any build tricks to filter out GWT stuff)? > > Perhaps then GWT-specific RF code like any of the client/rebind code > (and even GWT-coupled server code) should stay in c.g.g.requestfactory? > > Also, the new c.g.rf.shared.RequestFactory imports c.g.gwt's > EventBus--no idea if that's a big deal or not, but seems odd if > c.g.requestfactory is supposed to be reusable/non-GWT standalone > (which, may very likely be a constraint I'm making up--it just > seems elegant if non-GWT reuse is what you're after). > > - Stephen > > -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
