PropertyChanged
Avalonia
PropertyChanged | Avalonia | |
---|---|---|
14 | 254 | |
1,831 | 23,824 | |
0.7% | 1.6% | |
8.5 | 9.9 | |
11 days ago | 2 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.
PropertyChanged
-
Window Forms change notification
Add [AddINotifyPropertyChangedInterface] attribute to the class for change notification.
-
What does Realm.Fody do?
All the weaving libraries (also called weavers or addin) using Fody need to have the .Fody suffix, so it's quite easy to recognize them. As an example, if you ever had to implement INotifyPropertyChanged manually in a class with dozens of properties you would probably welcome weaving (and Fody) with open arms. By creating all the plumbing code directly in IL, libraries like PropertyChanged.Fody allows to inject the necessary notification code without the need to modify anything in the original source code.
-
[Library] Call all IEnumerable<T> via a single injected T
You can rewrite auto-props (as used this this lib https://github.com/Fody/PropertyChanged) with Fody.
-
Double programming meme
If you're not familiar with Fody and specifically the PropertyChanged weaver, I highly recommend checking it out: https://github.com/Fody/PropertyChanged
-
Is it just me, or is WPF just harder to work with than WinForms?
Now the ugly part - you need to implement INotifyPropertyChanged. It can be done either manually, or automated with this or this
-
What can be done to make the switch from WinForms to WPF easier?
https://github.com/Fody/PropertyChanged and Android background makes WPF pretty easy. At least the surface level stuff.
-
Automated nameof(Field)
If you really don't want to deal with it ever again, just add this Fody - PropertyChanged NuGet package. Any class that inherits from INotifyPropertyChanged will be updated at compile time to inject in the boilerplate code for handling the property change and you never even need to think about it again. All you need to do is just add plain old properties. The only downside that some people see is that it is not immediately transparent as the change notification code is injected in during compile and is not in source code.
-
We Just Gave $154,999.89 to Open Source Maintainers
And GitHub is the place where employees of billion dollar companies pester unpaid maintainers because they won’t support a 12 year old version of .NET
https://github.com/Fody/PropertyChanged/issues/270#issuecomm...
-
Can anyone give me an example of how they use fody to simplify the Get;Set; with property changed?
If you need more info, check the docs https://github.com/Fody/PropertyChanged
Avalonia
-
Industrial Controller? Windows or Linux?
You might also want to look at AvaloniaUI[0] for a cross platform .NET GUI library. It is similar to WPF but much nicer to work with.
[0] https://github.com/AvaloniaUI/Avalonia
- Avalonia – Farewell to the .NET Foundation
-
AvaloniaUI: Create Multi-Platform Apps with .NET
Production user here. There's no money gotchas. They're above reproach. In fact, I've received considerable free support from their devs on GitHub Issues [1].
The Avalonia business model is based on selling XPF, which runs WPF (Windows-only) apps on other platforms. That's very interesting to big corps with existing codebases.
See my comment [2]
[1] https://github.com/AvaloniaUI/Avalonia/issues
[2] https://news.ycombinator.com/item?id=39246988#39249128
-
.NET on Linux: What a Contrast
Yes, but the portable GUI frameworks by Microsoft themselves are generally not very good, and they tend to be abandoned after a couple of years.
Avalonia is developed outside of the Microsoft corporate madness and seems to be slowly becoming the defacto cross-platform framework because it is expected to last a bit longer than a manager's attention span: https://avaloniaui.net/
- Too many Mac apps are being built with Electron
-
Ask HN: Do you have a problem you'd pay to have taken away?
Not my comment, but relevant here "The problem with compiling Skia to WASM is you'll lose any benefits of hardware graphics acceleration on the device."
(From https://github.com/AvaloniaUI/Avalonia/discussions/6831#disc... )
- Dezvoltare aplicatie desktop
- Ask HN: How to create web, mobile, and desktop apps from a single code base?
-
.NET 8 – .NET Blog
It's a bit of a hit and miss as of today. CLI, back-end and natively compiled libraries (think dll/so/dylib or even .lib/.a - you can statically link NAOT binaries into other "unmanaged" code) work best, GUI - requires more work.
Avalonia[0] and MAUI[1] have known working templates with it, but YMMV.
[0] https://github.com/lixinyang123/AvaloniaAOT / https://github.com/AvaloniaUI/Avalonia/ / honorable mention https://github.com/VincentH-Net/CSharpForMarkup
[1] https://github.com/dotnet/maui (try out with just true in csproj - it is known to work e.g. on iOS)
-
One Game, by One Man, on Six Platforms: The Good, the Bad and the Ugly
For desktop, Avalonia, hands down.
https://avaloniaui.net/
Open source, powered by Skia, backed by JetBrains, and quite battle-tested at this point for small to medium-sized apps. In theory perfectly capable for enterprise as well, since it's basically a spiritual successor to WPF, which has been an industry standard for about 15 years.
They're diving into mobile and WASM well, but that's more of a recent effort and I haven't tested that yet.
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..
Uno Platform - Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
ReactiveUI.Fody - C# Fody extension to generate RaisePropertyChange notifications for properties and ObservableAsPropertyHelper properties.
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.
PropertyChanged.SourceGenerator - Powerful INotifyPropertyChanged / INotifyPropertyChanging Source Generator, which generates INPC boilerplate for you as part of your build. Supports features such as automatic and manual dependencies between properties, notifications when specific properties change, and more.
WPF - WPF is a .NET Core UI framework for building Windows desktop applications.
sentry-symfony - The official Symfony SDK for Sentry (sentry.io)
Eto.Forms - Cross platform GUI framework for desktop and mobile applications in .NET
sentry-javascript - Official Sentry SDKs for JavaScript
MahApps.Metro - A framework that allows developers to cobble together a better UI for their own WPF applications with minimal effort.
UWP Community Toolkit - The Windows Community Toolkit is a collection of helpers, extensions, and custom controls. It simplifies and demonstrates common developer tasks building .NET apps with UWP and the Windows App SDK / WinUI 3 for Windows 10 and Windows 11. The toolkit is part of the .NET Foundation.
Gtk# - Gtk# is a Mono/.NET binding to the cross platform Gtk+ GUI toolkit and the foundation of most GUI apps built with Mono