Any updates from any of you guys? Jesse, did you hear back from Bob? As an update for how I'm speeding up my bindings on Android, it seems like the worst source of most of the slow binding is binding generics via typeliteral. I just made a tremendous gain by being a human compiler and explicitly deriving about fifty or so concrete classes from my generic ones. I still have a lot of tedious work left to get my app to start up in a reasonable time (1-2 seconds). I've had to spend several very unpleasant weeks doing this.
I wish there were some way to generate the code for this or save the bindings via serialization so binding became a single compile-time or installation-time operation. Thanks, Jeff On Thursday, June 21, 2012 1:25:46 PM UTC-5, glenviewjeff wrote: > > FYI for those of you that hadn't already read the Roboguice group > thread<https://groups.google.com/d/topic/roboguice/BPcFafTsW9c/discussion>, > in order to support static injection, module bindings are executed twice > and double the startup binding times. Since I don't use static injection > and can't imagine why anybody would, I commented out the below loop > RoboGuice.setBaseApplicationInjector, rebuilt RoboGuice, and cut my startup > time almost in half. > > // Do a little rewriting on the modules first to > // add static resource injection > /* for(Element element : Elements.getElements(modules)) { > element.acceptVisitor(new DefaultElementVisitor<Void>() { > @Override > public Void visit(StaticInjectionRequest element) { > > getResourceListener(application).requestStaticInjection(element.getType()); > return null; > } > }); > } */ > > -- You received this message because you are subscribed to the Google Groups "google-guice" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-guice/-/zPJKG2wAEGUJ. 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-guice?hl=en.
