On 2013-05-20 21:52, Nick Sabalausky wrote:
WPF/XAML is first-party, therefore it's native by definition
regardless of whether or not it internally hands off to the older UI
code. Saying WPF isn't native is like saying that Quartz isn't native
just because it doesn't use...uhh, whatever the UI was called in Mac OS
9.
Besides, having access to all of MS's internal code, documents,
probably even some of the original developers still around, etc., is
naturally going to change the feasibility in a way that no third party
toolkit (which is exactly what we're talking about here) is
realistically going to be able to match.
In other words, despite your antagonism, I was implicitly **agreeing**
with your assertion that it's one a hell of an undertaking,
*especially* if you don't make use of native APIs under-the-hood.
I completely agree.
--
/Jacob Carlborg
