| Re: [eclipse-incubator-e4-dev] Fw: Declarative UI roundup? |
|
David, Comments below. David Orme wrote: That's something that struck me superficially looking at XAML. I.e., they're "just" using class names as the element names where it's more usual to use feature/property names for the elements. Of course for attributes, people always expect feature/property names, but for elements often people are surprised that the element name isn't a type name. That becomes more obvious when the same type of object can play a role in more than one feature. Of course if you have a single containment feature (as in window parenting), you don't have this problem and it seems quite natural to use types for element names, especially when it allows you to avoid using "xsi:type" or defining a plethora of substitution group elements to avoid xsi:type... This is like xsi:type I assume. Think of how you'd do this in JSON. It's important to have this information early...
|