RoboGuice 3.0

[Thomas Keller]

Hi Michael!

I've read around here a little and stumbled upon 3.0-alpha artifacts on Maven Central of RoboGuice, however, I haven't found even the smallest announcement of the 3.0-alpha release that seemed to went online a couple of days ago. Reading the commit logs the support of ActionBarSherlock and better performance, especially during the startup, seem to be niceties that come with the new major version.

Can you outline what exactly your plans are for 3.0, what has been accomplished, and if there is any BC breaking in the new version?

I'm especially interested in details on the performance front, as we work around time penalties that come from heavy injection use in views already.

Many thanks for your time,

Thomas.

[Michael Burton]

Hi Thomas,

The focus of RoboGuice 3 is on performance.  There are also some nice usability improvements based on feedback from the issues list. The branch is still under active development so it's not quite ready for others to use yet.  There are still some major contributions I'm waiting on to merge in, but expect a beta announcement some time in the next couple of months.

For the adventurous, here's a draft summary of what's gone into the branch so far:

Changes in 3.0:

• android 4.x dep
• event changes
• robolectric 2
• version number change
• various warnings cleanup
• add OnSaveInstanceState event (note: add context to this event)
• default binding to LnImpl
• remove RobolectricRoboTestRunner
• deprecate SafeAsyncTask
• add AndroidCallable for performance improvement
• SafeAsyncTask now uses AndroidCallable
• Ln can now be reconfigured
• don't get stacktrace in SafeAsyncTask if debug is not enabled
• include roboguice-sherlock
• remove static injection for performacne improvement

I can't support RoboGuice 3.0 yet, so please don't use it or expect me to answer questions about it on the mailing list just yet.  But work on the release is picking up and the beta should be out by October or November, at which time it will be fully supported.

Also, if you or anyone know of other specific opportunities to pick up performance improvements, I'd love to see pull requests or prototype work.

Cheers

Mike

--
You received this message because you are subscribed to the Google Groups "roboguice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roboguice+...@googlegroups.com.
To post to this group, send email to robo...@googlegroups.com.
Visit this group at http://groups.google.com/group/roboguice.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

--

http://about.me/michaelburton

[Harut Martirosyan]

Hey guys, any updates on this, at least a beta sneak preview or smth?

[Michael Burton]

You can always feel free to pull the head of the repo if you want to be on the bleeding edge :)  I won't be able to offer much support, however.

http://about.me/michaelburton

--

[Pavel Švéda]

Hi, based on what I see in master branch, it looks quite promising :-) Will you release a beta soon? Thx!

[Michael Burton]

That's a good question.  I don't have an answer yet... Stephane and I are working on some experiments that have led to positive improvements in app startup time, but we haven't quite finished productionizing them yet.  Once we do, I think that will be the point that we decide to release a beta.  My hope is that we have one by April or May.

http://about.me/michaelburton

On Sat, Mar 22, 2014 at 1:09 AM, Pavel Švéda <xsv...@gmail.com> wrote:

Hi, based on what I see in master branch, it looks quite promising :-) Will you release a beta soon? Thx!

--
You received this message because you are subscribed to the Google Groups "roboguice" group.
To unsubscribe from this group and stop receiving emails from it, send an email to roboguice+...@googlegroups.com.
To post to this group, send email to robo...@googlegroups.com.
Visit this group at http://groups.google.com/group/roboguice.

For more options, visit https://groups.google.com/d/optout.

[pumpk...@gmail.com]

Looking forward to 3.0 as well.. specifically the RoboPreferenceFragment.  Thanks for all the hard work guy.