LemurMadness

4 ms·

1. 1.▲
   by LemurMadness 9y ago

   It looks like there's two options for cross-platform XAML UIs: * Prism [1], which doesn't seem to support .NET Core. It was originally created by Microsoft Patterns & Practices, but then open sourced it. It's now commun
2. 2.▲
   by LemurMadness 9y ago

   I just spent some time working with Eto.Forms (based upon your recommendation, thanks!). It looks pretty nice and seems straight-forward. I also appreciate that it officially supports F# in addition to the regular C# and VB.NET. Unfortuna
3. 3.▲
   by LemurMadness 9y ago

   The main problem with Avalonia is that it's still in alpha. It looks like a good solution, though, so definitely something to keep an eye on if you're looking for a solution that doesn't require running a web server and rend
4. 4.▲
   by LemurMadness 9y ago

   I really like this approach, particularly since it allows a clean separation between the responsibilities of designing the UI and writing the back-end code. The UI designer can still wire up events and design them in Qt Creator (maybe usin
5. 5.▲
   by LemurMadness 9y ago

   That's good point. But one big difference between Xwt and Xamarin Forms is that Xwt supports Linux via GTK (GTK1, GTK2 & GTK3) whereas Xamarin Forms does not. Xamarin Forms also requires different code for different targets, such a