Rob Relyea - XAMLified - All Comments

re: PDC08 News: XAML in .NET 4: XAML2009 & System.Xaml.dll

Denis Vuyka — Thu, 20 Nov 2008 13:36:06 GMT

Are there any public dates for the coming CTP? I really hope System.Xaml will be available during the next 10 days of November...

re: PDC08: XAML Talk

Daniel Earwicker — Wed, 19 Nov 2008 15:11:25 GMT

Love the enhancements to XAML, especially generics support.

The thing that is completely misleading about all this is calling it "declarative". I noticed this happening several times in the talk, simply because something had been re-expressed in XML.

If you take the C# source of an imperative program, with switches, ifs, assignments, loops, etc. and translate it into a XAML dialect that incorporates "activity" objects corresponding to all those imperative steps, how has it become "declarative"? There's a perfect bijection between the imperative steps in the two versions. They're fundamentally identical. Just because something is encoded in XML does not make it declarative. Equivalently, it's possible to write declaratively in C# using object initialization syntax, so just because it's not in XML, doesn't mean it's not declarative. You could take any XAML tree and turn it into a C# object initalization tree and it wouldn't get any less declarative.

The more complete the XAML support for imperative programming becomes, the more it may lose its value or focus as a place where we only find declarative constructs. It starts instead to become a general purpose programming language - albeit one that cannot help being clunkier and more needlessly verbose than most existing languages, being based on XML.

Dew Drop - November 19, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - November 19, 2008 | Alvin Ashcraft's Morning Dew — Wed, 19 Nov 2008 13:48:21 GMT

Pingback from Dew Drop - November 19, 2008 | Alvin Ashcraft's Morning Dew

re: The 8 Benefits of XAML for UI and Beyond

Denis Vuyka — Tue, 18 Nov 2008 08:34:33 GMT

Rob,

As for XamlReader/XamlWriter PDC, it was a brilliant talk and awesome news. Waiting impatiently for November CTP.

Guess there will be a "DOM box" age on Codeplex starting from December :)

Dew Drop - Weekend Edition - November 15-16, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - Weekend Edition - November 15-16, 2008 | Alvin Ashcraft's Morning Dew — Sun, 16 Nov 2008 02:42:39 GMT

Pingback from Dew Drop - Weekend Edition - November 15-16, 2008 | Alvin Ashcraft's Morning Dew

2008 November 09 - Links for today « My (almost) Daily Links

2008 November 09 - Links for today « My (almost) Daily Links — Sun, 09 Nov 2008 07:28:00 GMT

Pingback from 2008 November 09 - Links for today « My (almost) Daily Links

re: Know of any WPF podcasts?

olicea — Sun, 09 Nov 2008 02:16:57 GMT

check the WPF podcasts in channel9

channel9.msdn.com/.../Podcasts

Silverlight News for November 07, 2008

Silverlight News for November 07, 2008 — Fri, 07 Nov 2008 08:19:24 GMT

Pingback from Silverlight News for November 07, 2008

re: The 8 Benefits of XAML for UI and Beyond

Rob_Relyea — Thu, 06 Nov 2008 22:23:13 GMT

Denis-

Just to clarify...XamlReader/XamlWriter that I mention are not the same X->O or O->X APIs from .NET 3. They are now abstract classes which are more similar to XmlReader/XmlWriter. Go watch the PDC talk on XAML to learn more.

Thanks, Rob

The 8 Benefits of XAML for UI and Beyond

WPF, Silverlight and .NET Musings — Thu, 06 Nov 2008 21:35:15 GMT

WPF team's PM Architect Rob Relyea wrote up a good post today summarizing the benefits of XAML for UI

re: The 8 Benefits of XAML for UI and Beyond

Denis Vuyka — Thu, 06 Nov 2008 18:09:41 GMT

My favorite thing is ISupportInitialize support that DataContractSerializer lacks. Great that XamlReader/XamlWriter get more common namespace.

re: The 8 Benefits of XAML for UI and Beyond

Rob_Relyea — Thu, 06 Nov 2008 17:48:06 GMT

Tanveer-

I had mistakenly defined Book.Year as a string originally. Somebody else caught that mistake and I've updated it to an int. So the change you suggest is no longer necessary.

Thanks, Rob

re: The 8 Benefits of XAML for UI and Beyond

Tanveer Badar — Thu, 06 Nov 2008 17:41:03 GMT

Shouldn't

Works:

b1.Year = 2000;

Compile Time Error:

b1.Year = "6/1999";

Compile Time Error:

b1.Year = 2000;

Works:

b1.Year = "6/1999";

re: The 8 Benefits of XAML for UI and Beyond

Krishna Vangapandu — Thu, 06 Nov 2008 17:39:14 GMT

Agreed XAML is great and you guys are doing great job on it. Especially the new XAML with support for non-def constructors and generics.

But

BookList bl = new BookList();

Book b1 = new Book();

b1.Author = "J. K. Rowling";

b1.Title = “Harry Potter and the Philosopher’s Stone”;

b1.Year = 1997;

bl.Add(b1);

Book b2 = new Book();

b2.Author = "L. Frank Baum";

b2.Title = “Wizard of Oz”;

b2.Year = 1900;

bl.Add(b2);

BookList bl = new BookList(){

new Book(){

Author = "J. K. Rowling",

Title = “Harry Potter and the Philosopher’s Stone”,

Year = 1997

new Book(){

Author = "L. Frank Baum",

Title = “Wizard of Oz”

Year = 1900

}

};

C# is sweet too!

By the way, I am eager to get my hands on your new XAML Pad. Hopefully you would integrate the step-by-step loading(like f11, the one you mentioned in the talk).

re: The 8 Benefits of XAML for UI and Beyond

Brian Chapman — Thu, 06 Nov 2008 16:53:27 GMT

When using XML (or any file format) to load and store data you have to maintain 3 systems. 1) The classes that will hold the data at runtime. 2) The file loading and storing module. Even using XmlReader there is significant processing to get the XML data into your data structures. 3) The data files themselves.

With XAML: #2 is done for you, and is yet general enough to do nearly everything you want.