> That is exactly what I was trying to get at. I understand that XAML > provides UI controls in a similar fashion to SPARK. This just gets > straight back to what my original statement was (though it was > originally done only have seriously): > XAML does not provide UI Controls. Avalon (the new GUI API) provides the UI Controls, and XAML can be used to express them XML form, rather then procedural code (via constructos and set properties).
XAML does not have a schema, since it is open ended. Any .Net object can be expressed using XAML. IMHO, that is one of the major drawbacks of SPARK and XUL. They only understand a predefined set of controls, and provide the very limited ability to create custom controls. The old SVG-RSS part of the SVG 1.2 spec was a step in the right direction to give SVG the ability to create custom controls, but I've been out of the loop, and don't know what happened with that in the SVG 1.2 spec. XAML is the natural evolution of the Microsoft Element and Binary behaviors, and anyone who was around this board back in the 2000/2001 time frame knows how much I loved using element/binary behaviors with SVG. Element/Binary behaviors had a lot of flaws, but was a good proof of concept (definately not really ready for prime time though). A lot of the XAML team at MSFT were part of the team that created element behaviors. Alastair, if you could implement SPARK using Java, that would rock! Don ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
