forked from roboguice/roboguice
-
Notifications
You must be signed in to change notification settings - Fork 0
MakingContributions
Mike Burton edited this page Feb 4, 2013
·
2 revisions
If you'd like to experiment with your own changes to RoboGuice, we encourage you to make your own clone and play away.
Here are some best practices for how to use a clone.
- If you don't have one already, fork the repository by clicking Fork button.
- Hack on your changes.
- Send a pull request
Note sure how to fork a repo? Learn how here.
- 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