Windows Now

A user asked: Is there a generic way of assigning a property a value, somewhat like you could do through XAML? For example, if I specify the following code: <Glyphs Fill=”#000000”> How would I create a Fill property with value “#000000”

Jon Udell compares Flex and Avalon . He says: It's interesting to consider these two admirably compact implementations side-by-side. Some points of comparison: MXML XAML Here today 2006? 2007? Runs anywhere Flash Player 7 runs Runs only on Longhorn Server

My post today on microsoft.public.windows.developer.winfx.general I hope Microsoft also does some serious long term testing of Longhorn. I'd hate to think that everyones WinFS could grind to a halt after adding 6 months worth of data and no one could

Apologies for not posting in a long time. I guess you'd all though this was another blogging casualty. But I'm back. I'm still working mainly with VB6 but I'm taking every oppotunity to cram .Net from books articles and videos online. I really like the

Dino's Un-Programming post, brings up interesting feedback from the development community. We want to make XAML somethings that developers can choose to use. That being said, I hope tools like VS and other tools from the rest of the industry focus on

I just saw Kenny Lim's ( digitalnetbizz ) posting calling out using a CLR object as a property in XAML . Let me give people some background on the feature and some changes we are considering in the future. Markup==ObjectModel This is one of the Avalon

WinFX allows you use XAML to declaratively define your UI, interactive media, or document. XAML is a great way to define these things. However, XAML isn't what we'd prefer to use at runtime. With HTML, parsing of the .html file is done at runtime. This

Although this article is a couple weeks old (and I dont know if someone already posted it) I thought it was quite an interesting read on WinFX and its relationship to the .NET Framework today as well as to the Win32 API. It cleared up a few things for

Yesterday Chris , Don , Martin (a coworker of Don's) and I met to discuss XAML. We're going to be thinking hard about possible improvements to it. Now when I say XAML in this context - i mean the markup format, not the Avalon elements or animations, etc

I'm not sure how Avalon is going to go on the ID vs Id issue. Thanks to Brad and Steven for raising the issue with the community. I've read every reason, tallied the results, took out the repeat votes (but left their first vote in), took out Microsoft

Daniel raises the issue of attached properties and shows how WXS could be used for validation. That looks like it is one way to solve the problem of attached properties. But could it work in all XML Editors? We currently provide: a schema - xaml.xsd

In the comments of Steven's posting about the SideBar usability study, Frank says: “It is good that usability is being tested for Avalon. Looking at the docs online, I have the feeling it is one of the least-usable APIs I have ever seen. The xml

We just posted a patch to make intellisense in xaml better. The problem was that the XML editor in VS has some things hard coded. It thought that if a file didn't have .xml as an extension, it must not be XML. No matter how much we told it that our <style>

Don was showing how XAML was not just about building trees of Avalon Elements with his K&R flashback . That's true: XAML can be used to build (a) element trees, (b) element trees with logic, or (c) class definition. I don't want people to become too focused

In a comment , George Mladenov asked: Why does XAML need to be (well-formed) XML in the first place? XQuery is not XML and yet it’s way better than XSLT, since its syntax is more expressive, readable, and intuitive. XAML does need to be interoperable

My demos have been posted for a while. My slides must have gotten lost in the mail... Now it all seems to be posted: http://msdn.microsoft.com/events/pdc/agendaandsessions/sessions/default.aspx My session was CLI300. Let me know if you have any questions

I'm going to try to start posting my comments answers that others may find good info in on my blog, not just as comments on people's site. Sam Gentile posted : I just realized that the Longhorn SDK adds templates to VS.NET Whidbey so you can use it to

So I've described the 5 families of Avalon Elements : Panels, Controls, Shapes, Decorators, & ContentElements. In order to describe how XAML is used to build Element Trees (see XAML: Element Trees, Element Trees + Logic, or Class Defintion ), here is

There are 3 main ways to use XAML. 1) to define a tree of elements with animations, databinding, etc... 2) to define a tree of elements (as in #1) with programming logic behind it 3) to define a new class #1 doesn't require compilation of the xaml. I

XAML has been discussed a bunch lately. It is easiest to show people what it is in person, but since that won't scale, I'll try to convey the same points by posting markup samples, descriptions and screenshots. Avalon, Longhorn & XAML Avalon is a presentation