3 ms·

It's a valid point, simply because browser UI kits are outdated, memory hogs, and have a ton of legacy cruft. I've recently been using Windows Forms with C# ag

It's a valid point, simply because browser UI kits are outdated, memory hogs, and have a ton of legacy cruft. I've recently been using Windows Forms with C# again and am amazed at the ease of use, if only they had made styling easy this framework would have been a gold standard for years to come. It's even cross platform too thanks to Mono.

Const-me 9y ago
Windows forms is based on decides old WinApi. There's some support for styling there, e.g. owner drawn items, custom painted controls, but using it correctly is tricky as hell. WPF is based on Direct3D 9, and is easily stylable. I consider it is the gold standard. But it is Windows only. There are cross platform alternatives, xamarin, avalonia, but I don't have hands on experience with them.
seabrookmx 9y ago
> would have been the gold standard for years to come I've written a lot of webforms and do really like it for "quick and dirty" UI's, but it has a lot of limitations that make it a bad choice for non-trivial apps. Off the top of my head: -styling -resizing (text reflow and re-layout of items is very hard to get right/working) -screen scaling (non-integer, say 150%) I also found it requires a ton of boilerplate code to programmatically change the UI. That said, my favourite part is the first class support for events. Knowing this paradigm made my shift to Qt (which has something similar called signals) much easier.