4 ms·
The funny thing is that he's primarily after unidirectional data flow and anti-data binding. I can actually get behind that. I worked on several large WPF pro
by nightski 9y ago
The funny thing is that he's primarily after unidirectional data flow and anti-data binding. I can actually get behind that. I worked on several large WPF projects many years ago and TBH I don't think it would be impossible to implement a uni-directional/redux style system within WPF. Would be an interesting project.
IF WPF was still the primary UI tech on Windows I probably could get behind implementing such a library.
- dman 9y agoWhat is the primary UI tech on Windows now?
- pjmlp 9y agoXAML, which is the same XML description language as WPF uses, plus the backing UWP controls, which are also quite similar to the WPF API. Main differences is that XAML processing is implemented in C# in .NET, and in C++/CX on UWP. XAML on UWP supports static binding at compile time, and on WPF it is only dynamic (x:Bind vs Binding). Finally the actual classes backing the UI components aren't 100% compatible, but do have most of the same methods and properties. Anyone that knows WPF, shouldn't have any issue with XAML/UWP.
- int_19h 9y ago> Main differences is that XAML processing is implemented in C# in .NET, and in C++/CX on UWP. Most stock UWP components (the ones that come with the OS) are implemented in pure C++ using WRL (https://docs.microsoft.com/en-us/cpp/windows/windows-runtime-cpp-template-library-wrl https://docs.microsoft.com/en-us/cpp/windows/windows-runtime...). This is mainly because they were already being actively implemented long before C++/CX became usable.
- pjmlp 9y agoThanks for the clarification.
- douche 9y agoDay to day, it's as often as not Win32 or it's thin .Net wrapper, WinForms.
- tonyedgecombe 9y agoWinForms is very productive but if you want high dpi support its hard work.
- pjmlp 9y agoUnless one has Windows 10 Creators edition/.NET 4.7.
- tonyedgecombe 9y agoBut then you might as well go down the UWP road, most of us still have to support Windows 7 or even earlier.
- pjmlp 9y agoWPF is still the primary UI tech on Windows, UWP is built on top of it. Anyone that knows their way around WPF, can make use of XAML, MVVM and all related UI concepts, regardless of the API differences between WPF, Silverlight, UWP and Xamarin.Forms. For me they are all the same.
- nightski 9y agoI know that UWP uses XAML and has very similar concepts, but is it really built upon WPF itself? I was under the impression it was it's own library/codebase.
- pjmlp 9y agoIt is its own implementation, but anyone that knowns one can use the other quite easily.
- contextfree 9y agoMost people don't seem to know this but WinRT/UWP XAML was actually a fork (not a rewrite) of Silverlight. Silverlight had a C++ core layer and a C# API layer, WinRT XAML kept the core and replaced the C# API layer with a new WinRT API layer.