lambda-converters
ProjectReunion
lambda-converters | ProjectReunion | |
---|---|---|
4 | 53 | |
134 | 3,693 | |
- | 1.4% | |
0.0 | 9.3 | |
over 4 years ago | 8 days ago | |
C# | C++ | |
Apache License 2.0 | 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.
lambda-converters
-
WPF Begins its Long Goodbye
Yeah, I think some things go a bit too far. I also think they tried too hard to solve certain things (poorly) in XAML that frankly shouldn't be declarative. There's a few things you can do to make WPF less painful. I recommend using https://github.com/michael-damatov/lambda-converters, for example, rather than writing whole-blown converter classes of your own.
-
(rant/discussion/question) Why does wpf seem so overly complicated?
something like https://github.com/michael-damatov/lambda-converters should be built in because writing a whole-ass class is inexplicably verbose for 95% of things people do with converters
-
Example of something that WPF can do (functionality wise) and WinForms cannot? advanced feature?
instead of full-blown converters in C#, let me write inline lambdas right in the XAML. Blazor lets me do that, sort of. (I use https://github.com/michael-damatov/lambda-converters so I at least don't have to write entire types.)
-
Best alternatives for WPF for sustainability and free controls?
I haven’t dived too deep into MVU either, but at a glance, it seems more focused on lambdas. IMHO, one of the weak spots in MVVM/XAML is how much boilerplate you have to write for a converter, when oftentimes just a lambda would do. This lib helps, but it still isn’t inline with the rest of the UI.
ProjectReunion
-
The power of interoperability: Why objects are inevitable (2013) [pdf]
> why Microsft has ceased anything beyond legacy support for it
That is not true at all. DirextX is COM, UWP was COM based, WinRT is still COM, WinUI and the Windows App SDK is again based on COM. C++, C#, Python and Rust are all supported programming languages for the Windows App SDK thanks to - you guessed it: COM. The C++, C# and Rust language projections for it are still being constantly updated: https://github.com/microsoft/xlang
When they started Project Reunion (code name for Windows APP SDK) back in 2021, just before Windows 11's release, they decided to double-down on COM. Like hard.
https://github.com/microsoft/WindowsAppSDK/blob/main/docs/fa...
> Practically speaking, any language & runtime that can handle COM objects can support Windows App SDK
-
WinUI3 + WebView2
The issue is described here: WebView2 does not support passing in a CoreWebView2Environment · Issue #1170 · microsoft/WindowsAppSDK (github.com)
-
Ask HN: What is the best way to build a desktop app in Windows in 2023?
.. and how many of the Microsoft applications actually use WinUI3? As far as I can tell they're doing their own thing (Office) or are Electron (Teams) or, at least in Windows 10, haven't actually been updated from WinForms.
The overhead of WinUI3 is pretty huge. The visual designer, a winning feature of Visual Studio for decades, is AWOL. Why? It's XAML, the same as the previous XAML designer! It's just .. broken?
The backward compatibility story is a disaster: you can get stuck in the UWP sandbox https://github.com/microsoft/WindowsAppSDK/issues/1780
What's the big Microsoft WinUI3 flagship app, then? Something people are actually using? Rather than just a few system dialogues. (How many Win11 settings pop up a Win32 dialogue box, still?)
- How can i change the pointer of my cursor in winui3?
- Leaked Microsoft poll shows fewer employees have confidence in leadership
-
For the past year and a half I've been working on Wintoys, an app that let's you experience Windows in your way and keep it fresh everyday while having everything you need in one place
Development for WinAppSdk and WinUI 3 is also very slow and Microsoft seems to not want to push it and invest more developers into it for some reason. They try to improve the framework, is just it's a small team. For example it was a headacke to apply the Mica backgrop and required unmanaged code, they made it simpler and reduced it to a line of code but it took months. I have 2 out of 7 issues fixed on WinAppSdk repository and 0 out of 8 issues fixed in the WinUI 3 repository (some of the older than a year). This are just my issues, there are many other opened by other developers. So yeah, it wasn't fun at all. PoweshellSDK had an issue with the Import-Module command and it wasn't fixed for more than a year and probably won't be ever fixed, but I'm glad I found a workaround, even more clean and more safe, otherwise I couldn't have added the posibility to uninstall and change Store apps.
-
Has MAUI improved last couple of months?
As far as I know, there are still some issues with OIDC integration. See this, for example.
- WPF Begins its Long Goodbye
-
File Explorer will soon be a Windows App SDK app
this I'm interested in. WinAppSDK is open source.
-
Why Modern Software Is Slow
I think the issue is actually the sandboxing and other stuff. WinRT StorageProvider API is known to be extremely slow and NTFS / Windows IO subsystem is itself already quite slow compared to UNIX. The issue IIRC is that StorageProvider is designed for sandboxing and the way they implemented that involves doing RPCs to other processes. So there's probably some heavy context switching involved, but it's architectural, and so the voice recorder was never fixed.
https://github.com/microsoft/WindowsAppSDK/issues/8