Flex 开发的 Mate、Swiz 和 Robotlegs 框架比较
My company is willing to reffactor its biggest and heaviest project introducing some kind of framework. Are there good online source/issue/blogpost with comparison of these 3 frameworks - Robotlegs, Swiz and Mate?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
我不认为比较是可行的方法。他们都有优点和缺点。这一切都取决于您想要实现的目标。
话虽如此，我个人的两个选择是 RobotLegs 和 Parsley。 RobotLegs 非常适合中小型应用，因为它易于学习和使用。 Parsley 比 RobotLegs 更强大，并且添加了更多功能，这就是它被用于世界上最大的柔性应用程序的原因。从你的描述来看，这似乎是一个很大的项目，那么我会推荐Parsley，但也许你不需要它的所有功能。
您能做的最好的事情就是尝试两者，看看哪一个最适合。
I don't think a comparison is the way to go. They all have strength and weaknesses. It all comes down to what you're trying to accomplish.
With that said, my 2 personal choices are RobotLegs and Parsley. RobotLegs is good for small to medium size application since it's easy to learn and use. Parsley is more robust and adds a lot more features than RobotLegs, which is why its been used in the world's largest flex applications. From your description, it seems this is a large project, then I would recommend Parsley, but maybe you don't need all of it's features.
Best thing you can do is try both and see which one fits best.
您尝试过谷歌搜索，对吧？快速谷歌搜索后发现了许多页面进行比较。为什么选择这 3 个框架？凯恩戈姆或欧芹怎么样？
我最终使用了 Robotlegs，因为我喜欢它的最小化，而且我喜欢通过元数据进行依赖注入（作为一个使用 Java 的 Spring 用户）。
另一个问题是为什么要重构添加框架？预期收益是什么？如果没有预期的好处，为什么要这样做呢？
You have tried googling, right? A quick google turned up numerous pages doing comparisons. Why those 3 frameworks? What about Cairngorm or Parsley?
I ended up using Robotlegs because I liked that it was minimal and I like dependency injection via metadata (being a Spring user with Java).
The other question is why refactor to add a framework? What is the expected benefit? If you don't have an expected benefit, why do it?
我的 Flex 简介应用程序的架构可能会有所帮助，因为在本文中，我没有比较框架，而是列出了所有架构框架需要解决的常见问题，以及一些关于不同框架如何处理的代码片段接近解决方案。当要理解为什么某个框架以某种方式设计时，理解常见问题至关重要。
My Introduction to Flex Application's Architectures could be of help, because in this article instead of comparing the frameworks I list the common problems all architectural frameworks need to address as well with some code snippets on how the different frameworks approach the solutions. Understanding the common problems is crucial when it comes to understand why a certain frameworks is designed in that certain way.
似乎没有太多关于 Robotlegs 的资源。
It seems that there aren't a lot of resources out there covering Robotlegs.