Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Wolfgang Riedmann" Newsgroups: comp.lang.clipper.visual-objects Subject: Re: Re X# and VULCAN and VO.. quick story of way forward Date: Mon, 26 Feb 2018 13:43:07 +0100 Lines: 27 Message-ID: References: <83v79d93skc6cftc0ds7mrh1qcnt3o128f@4ax.com> X-Trace: individual.net WlYc2H0D90OGwslsHYFNGArLhi0Z+H3c2wduCaWTAwhPJUhb4= Cancel-Lock: sha1:2geXXNfEyiQoE1ZJReRMvJ7gVFs= User-Agent: XanaNews/1.18.1.6 Xref: csiph.com comp.lang.clipper.visual-objects:11435 Hi Karl, > > Unfortunately it is not possible use XAML with a non-Microsoft > > application, > would you care to elaborate a bit? Steering clear from WPF up2now , > i always thougth XAML as a standardized language to describe screens > and their behaviour, why shouldn't that work without VS/MS? Chris has invested some time, and tried several times to integrate XAML compilation in XIDE, but failed. Of course you can load XAML stylesheets at runtime (that is what I do), but it is not possible to compile XAML to BAML. AFAIK it is Visual Studio that does the XAML-to-BAML compilation, and only the BAML is added as resource to the executable. And for example it is not possible to inherit from a XAML based window - the approach we have done for ages in VO (you can do it, but there is some additional code needed). I will show some code at the Koln conference that demonstrates the power of WPF. Wolfgang --