forked from roboguice/roboguice
-
Notifications
You must be signed in to change notification settings - Fork 0
Roadmap
Donn Felker edited this page Oct 12, 2012
·
1 revision
An outline of where we expect RoboGuice to go
- Fragment support
- Ability to inject in custom views
- Guice3
- Maven3
- Finally build easily without manually dealing with dependencies
- Improve ContextScope to reduce churn and duplication? What about concurrency issues?
- Refactor application and module code to simplify Getting Started docs
- Turn ExtraConverter into a generalized conversion system
- For Projects Using Maven
- For Non-Maven Projects
- Inheriting from RoboGuice Classes
- (Upgrade Instructions for Users of RoboGuice 1.1)
- Your First View Injection
- Your First Resource Injection
- Your First System Service Injection
- Your First POJO Injection
- Your First Singleton and ContextSingleton (wiki/Understanding Scopes)
- Your First Custom Binding
- Your First Injected Fragment
- Your First Injected Service and BroadcastReceiver
- Your First Testcase
- Your First Injection into a Custom View class
- Your First Injected Content Provider
- How Injection Works
- When Injection Just Works, and when you have to call injectMembers()
- The Difference between Global and Context-scoped Injection
- Analyzing a Guice Stack Trace
- What's the difference between Nullable and Optional?
- Remove or replace RoboGuice's default bindings
- Use your own BaseActivity with RoboGuice
- Inject into an object that you don't instantiate
- Dealing with Circular Dependencies
- Work with Library Projects
- Deal with ComputationException due to StackOverflowError
- Taming Fragmentation using RoboGuice