I did some investigating, and I wasn't to happy with what I found out. You can read about how Longhorn's XAML makes a mess of markup in my blog: http://myxaml.com/marcclifton
To summarize: 1. Tag names are not just class names--they can be function calls, class types, mystery property setters, or have no relationship to the underlying DOM at all! 2. Implicit collection tags - Longhorn's XAML parser has hidden knowledge of the DOM so that you don't have to use collection tags in your markup 3. Decorators and VisualStyle violate every rule in the XAML book I think this spells disaster for the idea that XAML (at least Longhorn's version of it) will be a viable cross-platform serialization syntax. Suffice it to say, I won't be implementing any of these custom parser hacks in MyXaml. Marc ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ xul-announce mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xul-announce
