Android-Binding 和 Roboguice 怎么样？
作为 Android 开发的初学者，我正在学习的代码示例看起来有些杂乱，难以测试甚至难以理解。所以我遵循了这篇文章的建议：使用 Roboguice 进行依赖注入？ 并尝试使用 Android 绑定和机器人吉斯。但我现在担心他们到底有多好。
- 它们对于所有 Android 项目（包括具有多个视图的项目）来说是否足够好？
- 使用这些工具构建应用程序后，与不使用这些工具相比，该应用程序的性能如何？使用这些工具有什么问题吗？
- 还有其他工具可以帮助我实现敏捷/TDD 吗？
As a beginner for Android development, code samples I am learning from look somewhat disorganized and are hard to test or even to understand. So I followed this post suggested: Using Dependency Injection with Roboguice? and am trying to use Android-binding and Roboguice. But I am now worrying about how good they really are.
- Are they good enough for all Android projects including ones with a couple of views?
- After building an app with these tools, how is the app's performance in comparison without the tools? Any problem with using these tools?
- Is there any other tool that can help me for Agile/TDD?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我只使用过 Roboguice，这是我对它的看法。
Roboguice 源自 Guice。因此，它并不是真正为移动环境而构建的依赖注入框架。话虽如此，它可能会给您的应用程序带来相当大的开销。
另一方面，我还没有看到任何移动应用程序达到真正需要依赖注入的复杂性。我有一个使用 Roboguice 的应用程序，但很快我意识到它使我的应用程序变得比需要的更加复杂。所以我把它去掉了。我想这在很大程度上取决于您的应用程序的规模。
I've only used Roboguice and this is my opinion of it.
Roboguice is derived from Guice. So it's not really a dependency injection framework built from the grounds up for mobile environment. That being said, it can cause quite some overhead to your app.
On the other hand, I haven't seen any mobile app that reached a complexity that really needs dependency injection. I had an app the used Roboguice, but soon I realized that it's making my app more complex than it needs to be. So I stripped it out. I guess this depends a lot on the scale of your app.