>>I know that Avalon is an XML based GUI.
>>
>>I have some questions about the way it work.
>>Is this only a "local machine" thing or can we deliver Avalon stuff from internet?
>>
>>How this renderer is called? Do we have to open Alavon and load an Avalon document like we open an HTML or Word file?
>>Or an Avalon file is pre-compiled as an exe and started like a normal program?
>>
>>I think about this because I already do a lot of HTML, XML, SVG from fox and if the Avalon XML is rendered in the same fashion that an html file is, this is a relly ggod new for all of us. We already have some really cool framework to produce html (Web connection, AFP and others) and it could be relatively easy to add some classes to those framework to handle Avalon xml.
>
>Avalon forms are like .NET WinForms. Forms executed packaged in pre=compiled EXE files. You will need to run the EXE on a machine that has the .NET Framework and Avalon runtime files installed. Avalon uses XAML and .NET code behind it as source to compile. So if you were to use VFP to create or modify a XAML file in a VS project, you would need to rebuild the EXE. Avalon is still in development and won't be released until around next year (after VS 2005), so the compiling XAML details may change. This will all impact how VFP interacts and uses Avalon via interop as part of Sedna.

Too bad :(

I was dreaming of some cool vfp driven gui...