c# - ReactiveUI and Caliburn Micro together? -
i've been doing prototype work on new silverlight application using caliburn micro our mvvm framework. team has been happy it. in order address issues throttling requests services, suggested reactiveui's reactivecollections , implementation of inotifypropertychanged.
does have experience around using 2 together? since both mvvm frameworks, there's bit of overlap, wonder if might more trouble it's worth try , make them work together.
some of things caliburn micro are:
- the convention based binding, etc...very nicely done in our opinion.
- bootstrapping. way handled, it's easy extend when need to, out of box stuff works many of our use cases.
- composition/screen management. rob's notion of conductors, screens, etc. flows nicely us.
the reactiveui stuff has drawn (at least initially).
- the reactive collections , inotifypropertychanged stuff. particularly ability throttle reactions.
- reactive's asynchronous stuff seems bit cleaner deal rob's co-routine implementation.
i've barely had chance play reactiveui yet, looking @ , seeing overlap between two, wondered might have tried work both project. haven't been able find via google (which fault).
i'd love know if tried this; issues did have? parts of each framework did use , why? there examples or blog posts out there on using them together?
cheers,
steve
use both! this blog post should of way there - it's easy take existing viewmodels use other frameworks , "rxui'ify them". way can try out reactiveui on single viewmodel without having pick either caliburn micro or rxui.
Comments
Post a Comment