ReactiveUI 和 Caliburn Micro 一起？
我一直在使用 Caliburn Micro 作为我们的 MVVM 框架对新的 Silverlight 应用程序进行一些原型工作。团队总体上对此感到满意。为了解决对服务的请求限制的一些问题，有人建议我研究 ReactiveUI 的 ReactiveCollections 及其 INotifyPropertyChanged 的实现。
有人有将两者一起使用的经验吗？由于它们都是主要的 MVVM 框架，所以有很多重叠，所以我想知道是否可能比尝试让它们一起工作更麻烦。
我们真正喜欢 Caliburn Micro 的一些事情是：
- 基于约定的装订等......我们认为做得非常好。
- 引导。我们喜欢这种处理方式，在需要时很容易扩展，但开箱即用的东西非常适合我们的许多用例。
- 构图/屏幕管理。我们真的很喜欢罗布关于导体、屏幕等的概念。它对我们来说非常流畅。
ReactiveUI 的东西吸引了我们（至少在最初）。
- 反应式集合和 INotifyPropertyChanged 的东西。特别 抑制反应的能力。
- Reactive 的异步内容似乎比 Rob 的协同例程实现更容易处理。
我还没有机会使用 ReactiveUI，但当我查看它并看到两者之间的重叠时，我想知道谁可能尝试将两者都纳入一个项目中。我无法通过谷歌找到任何东西（这很可能是我的错）。
我很想知道你是否尝试过这个；你有什么问题吗？您使用了每个框架的哪些部分以及为什么？有没有关于一起使用它们的好例子或博客文章？
干杯，
史蒂夫
I've been doing some prototype work on a new Silverlight application using Caliburn Micro as our MVVM Framework. The team has generally been happy with it. In order to address some issues with throttling requests to services, it was suggested that I look into ReactiveUI's ReactiveCollections and their implementation of INotifyPropertyChanged.
Does anyone have any experience around using the two together? Since they are both primarily MVVM Frameworks, there's a good bit of overlap, so I wonder if it might be more trouble than it's worth to try and make them work together.
Some of the things we really like about Caliburn Micro are:
- The Convention based binding, etc...Very nicely done in our opinion.
- Bootstrapping. We like the way this is handled, it's easy to extend when you need to, but the out of the box stuff works well for many of our use cases.
- Composition/Screen Management. We really like Rob's notion of conductors, screens, etc. It flows very nicely for us.
The ReactiveUI stuff that has drawn us to it (at least initially).
- The Reactive Collections and INotifyPropertyChanged stuff. Particularly
the ability to throttle the reactions. - Reactive's asynchronous stuff seems a bit cleaner to deal with than Rob's Co-routine implementation.
I've barely had a chance to play with ReactiveUI yet, but as I was looking at it and seeing the overlap between the two, I wondered who might have tried to work both into a project. I haven't been able to find anything via Google (which could well be my fault).
I'd love to know if you tried this; what issues did you have? Which parts of each framework did you use and why? Are there any good examples or blog posts out there on using them together?
Cheers,
Steve
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
两者都用！ 这篇博文 应该可以帮助您了解大部分内容 - 实际上很容易采用现有的 ViewModel使用其他框架并“RxUI'化它们”。这样您就可以在单个 ViewModel 上尝试 ReactiveUI，而不必选择 Caliburn Micro 或 RxUI。
Use both! This blog post should get you most of the way there - it's actually very easy to take existing ViewModels that use other frameworks and "RxUI'ify them". This way you can try out ReactiveUI on a single ViewModel without having to pick either Caliburn Micro or RxUI.