ReactiveUI
Caliburn.Micro
Our great sponsors
ReactiveUI | Caliburn.Micro | |
---|---|---|
18 | 6 | |
7,897 | 2,767 | |
0.6% | 0.7% | |
9.0 | 4.0 | |
4 days ago | 10 days ago | |
C# | C# | |
MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ReactiveUI
-
Humble Chronicles: Managing State with Signals
ReactiveUI is based on Rx and very popular in the .Net world: https://www.reactiveui.net/.
-
Source generators run unreliably on VSCode and Rider? (MvvmToolkit)
I use PropertyChanged.Fody all the time and it works fantastically and consistently for implementing INotifyPropertyChange. It is even smart enough to understand dependencies within your get/set functions (should you choose to have custom ones) and notify that property if any of it's dependent properties change. While we are on the subject, if you are using MVVM with observables, you should really check out ReactiveUI. It is wonderful.
- What is a good alternative (or substitute) for MVVMLight?
-
System.Reactive v6.0.0-preview.1 available on NuGet
Personally I learned to use rx and observables by starting to use ReactiveUI combined with DynamicData for my WPF app MVVM architecture. It was maybe not to best choice out there, but I learned to work with it and some things it allows to do is awesome.
-
I want to learn WPF and was told I should use a MVVM based framework any up to date suggestions?
My favorite framework is Reactive UI but it's a bit more advanced than most MVVM frameworks since it uses Reactive Programming. You can still try its most basic features, though.
-
Which GUI framework should I learn: WinForms, WPF, Avalonia or something else?
There is a lot of overlap between WPF and Avalonia so I would start with either one of those. Most certainly Avalonia if you plan to do cross platform dev. I would also highly recommend that you learn and conform to MVVM and dependency injection for your architecture in order to write clean, maintainable, and testable code. My recommendation is ReactiveUI. It leans heavily on more modern patterns like Reactive extensions and IObservable and it can do so much more than just MVVM. As such, it is also very similar to Angular so the concepts will transfer easily if you ever need to do web development. On a side note, Pluralsight has a nice quick course on SOLID design principles. If your code is a mess, it would be a good idea to take a course on this though learning MVVM will be a big step in the right direction.
- Why is there a lack of cool repos?
-
WPF or WinForms
Also, about data binding and reactivity if you really enjoy WinForms, nevar forget!! https://www.reactiveui.net
-
Getting head around {get;set} for C# Models
Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).
-
Managing resource files for an app
Some projects like ReactiveUI take on a more webapp style project structure, with resources being in some static resources folder and all code being in a src folder.
Caliburn.Micro
-
caliburn.Micro: Difference between ActivateItemAsync and ActivateItem ?
It works with ActivateItemAsync but I don´t know if there is a difference that I should be aware of ? They seem to be a bit slow with updating the documentation so I´m a bit nervous about what else might not be updated yet.
-
Show HN: Async UI: A Rust UI Library Where Everything Is a Future
The programming model reminds me of Rob Eisenberg's older attempts at building UI toolkits ([0]). I don't recall if that was fully async or 'just' using a coroutine/generator-style approach, but it feels similar.
I'm not sure the complexity of doing everything using async constructs is worth it, though. Large-scale UI's built in Qt or Javascript are mostly single threaded anyway, but it's still worthwhile to explore so kudos for that. Looking forward to seeing how far you get.
-
Learning WPF
Vanilla WPF has a lot of boilerplate and verbose binding expressions. I'd check out an MVVM library like https://caliburnmicro.com/ which has tons of convention-based features and helps maintain the "screens" in your app.
-
Getting head around {get;set} for C# Models
Your UI needs to bind to something that can programmatically notify it about changes, we call these things View-Models. Usually View-Models implement INotifyPropertyChanged interface (another key interface is INotifyCollectionChanged that is responsible for notifying collection views that number of items is changed and they need to update the UI accordingly). You can do that (the implementation of the interface) manually or use some library to do that for you just to cut some boilerplate code (e.g. ReactiveUI + Fody or Microsoft.Toolkit.MVVM or maybe even this or this).
- Microsoft.Extensions.DependencyInjection to inject ViewModels into Views in AvaloniaUI app?
-
3rd party frameworks to add ease of use to XAML/WPF?
I haven't done WPF/XAML stuff in years but I really liked Caliburn Micro, largely because of the convention-based auto-binding.
What are some alternatives?
Prism - Prism is a framework for building loosely coupled, maintainable, and testable XAML applications in WPF, Xamarin Forms, and Uno / Win UI Applications..
contact - Retryable HTTP client in Go.
MVVMCross - The .NET MVVM framework for cross-platform solutions, including Android, iOS, MacCatalyst, macOS, tvOS, WPF, WinUI
MVVM Light Toolkit - The main purpose of the toolkit is to accelerate the creation and development of MVVM applications in Xamarin.Android, Xamarin.iOS, Xamarin.Forms, Windows 10 UWP, Windows Presentation Foundation (WPF), Silverlight, Windows Phone.
Stylet - A very lightweight but powerful ViewModel-First MVVM framework for WPF for .NET Framework and .NET Core, inspired by Caliburn.Micro.
WPF Application Framework (WAF) - Win Application Framework (WAF) is a lightweight Framework that helps you to create well structured XAML Applications.
LiveCharts2 - Simple, flexible, interactive & powerful charts, maps, and gauges for .Net, LiveCharts2 can now practically run everywhere WPF, WinForms, Xamarin, Avalonia, WinUI, UWP.
Introducing .NET Multi-platform App UI (MAUI) - .NET MAUI is the .NET Multi-platform App UI, a framework for building native device applications spanning mobile, tablet, and desktop.