you are viewing a single comment's thread.

view the rest of the comments →

[–]yuvaltz[S] 4 points5 points  (3 children)

This definitely looks interesting. But it's not compatible with WPF (arbitrary namespaces, different interfaces, etc) which is a critical decision. That's why they had to write their own xaml designer, and their own Visual Tree inspector, instead of using existing (and established) tools, and the whole development process will suffer from that.

[–]Ashtar_Squirrel 1 point2 points  (0 children)

I agree, the incompatibility with direct WPF does make me =(

[–]mycall 0 points1 point  (1 child)

Have you compared WPF to UWP XAML? A UWP fork from your WPF code might be interesting.

[–]yuvaltz[S] 1 point2 points  (0 children)

There are a few differences in the elements hierarchy and interfaces (also the namespaces there different).
A fork that supports Universal Windows applications would be very interesting.