Chris Anderson - "Hello Avalon"

Sweet

XAML is awesome. We will finally get to use a language similar to HTML to design Windows Application user interfaces. I can't wait to start using it!!

So, it sounds to me like XAML and Avalon will make designing a Longhorn client app very similar to designing and ASP.Net web application.  With the option of embedded code (in the markup) or code behind, and the markup defining the visual interface.

This is interesting and sounds cool, but I do have a few questions:

1.  Is my analogy correct?  Please give any comments correcting or extending this line of thought.

2.  Along the ASP.Net lines, most objects are server side, running in .Net.  If this is possible with Avalon (to some extent), does this mean at some point Longhorn apps could end up running in any compatible browser.  Markup + classes on the server (like ASP.Net) sounds like it would enable that...assuming MS published what would be required.

3.  If Avalon will be part of .Net, could it eventually make its way into the Mono project (or similar) (parts of it anyway)?  Would XAML be a public spec that could be used by others?

4. How would designing GUIs in XAML affect application performance?  Would it make it like rendering a web page locally (slow, but acceptable)?

Anyway, it's interesting stuff.  I look forward to reading your comments.

It all "smells" a lot more like writing HTAs in DHTML than it does something like an ASP.Net application.

I'd find it an incredible coincidence if HTAs were not in fact the inspiration.  Of course the universe is a pretty incredible place.

Homer wrote:

Would XAML be a public spec that could be used by others?

A very important question. Will Microsoft slap a patent on XAML or will it be available to anyone that wants to implement that schema?

/Lars.

Homer wrote:

4. How would designing GUIs in XAML affect application performance?  Would it make it like rendering a web page locally (slow, but acceptable)?

From what I've heard/read elsewhere the XAML code will be compiled by VS so the performance should be comparable to Windows Forms rather than HTML.

AndyC

Wow, I hadn't looked at XAML yet (been focussing on WinFS)... It really, really reminds me of an extension we wrote at my old job about 2 years ago which was basically "template-based windows forms". It wasn't anywhere near XAML, obviously, but it made a lot of our more common apps much, much more easy.

Fantastic, thanks guys!

Sorry if it's not the purpose of this thread, ut i've a question.
Is it possible to 'protect ' the interface produced in XAML.
For example in a company you did an application, and don't want users to modify it. Is it possible or do we only have to use c#, VB.Net... to create 'unmodifiable interfaces'?

ethan:

When developing an application your XAML will be compiled and not made available to users of the application.

Is that Carter Maslan interviewing him? He has a distinctive voice.

Nope, that was me.

want to know more about XAML.

Is this replacement for Macromedia's Flex ???
What is OS and platform compatibility ?

regards,
Sandip.