Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RFC: What are pain points with the ReactiveUI project as a user? #13

Open
glennawatson opened this issue Aug 6, 2018 · 8 comments
Open

Comments

@glennawatson
Copy link
Contributor

What are your pain points at the moment with RxUI?

Tell me and reply to this issue.

@nesterenko-kv
Copy link

It would cool to see support for custom DI-containers, as everyone adheres to their favorite.

@glennawatson
Copy link
Contributor Author

@nestquik See #14 about discussions how to approach that. Thanks for bringing it up.

@Massimo37
Copy link

Massimo37 commented Aug 7, 2018

UWP navigation...it's view-first and the way RxUI has implemented the VM-first approach has killed the niceness of the transition animations. It's currently just a flat-out hide/show approach.

@jcansdale
Copy link

Confusing threading exceptions when I referenced the ReactiveUI package in a WPF project without ReactiveUI.Wpf. That tripped me up at the first hurdle.

@matthewclendening
Copy link

Coming from the perspective of the ReactiveUI book (which is great by the way), the first section says to just do an “Install-Package ReactiveUI”. The book mentions that the “bait and switch” technique should take care of the dependencies. However, doing this in a top-level WPF platform project is not enough. The nuget package targets System.Reactive (>= 4.0.0), but Glen mentioned that at the moment RxUI is using System.Reactive 3.1.1 and you need to add a reference to System.Reactive.Compatibility til the next release of RxUI. I’m new to this, but just getting started with the build configuration currently published is not straightforward at all (at least with respect to WPF). Diving into this great library more every day.

@glennawatson
Copy link
Contributor Author

BTW ReactiveUI 8.4.1 was released this morning that has System.Reactive at 4.

@glennawatson
Copy link
Contributor Author

glennawatson commented Aug 7, 2018

The reasoning for the new ReactiveUI.WPF is Visual Studio for Mac unfortunately.

https://reactiveui.net/blog/2018/05/reactiveui-v8.0.0-released

If you target the WPF platform you now need to install the WPF specific package otherwise schedulers won't be wired up and you'll be greeted with an appropriate exception. The documentation has been updated. We had to make this change prevent Visual Studio for Mac from exploding when it encountered an automatically imported reference to Windows.Presentation which prevented these folks from being able to unit test their applications with Visual Studio for Mac.

ReactiveUI is a composable, cross-platform model-view-viewmodel framework for all .NET platforms that is inspired by functional reactive programming which is a paradigm that allows you to express the idea around a feature in one readable place, abstract mutable state away from your user interfaces and improve improve the testability of your application.

@ghuntley
Copy link
Member

ghuntley commented Aug 8, 2018

Getting reactiveui/ReactiveUI#1598 shipped will help folks out heaps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants