The problem with SVG does not have anything to do with SVG or Adobe, but with the W3C. SVG and most of the other W3C specs (well other then the XML ones), were not designed from the beginning to integrate with each other. Microsoft does not suffer from that ailment, since they are designing their APIs first, and then creating a standard way to express the APIs thru XML (which is called XAML). Avalon is the code name for the Graphics API, which can be expressed in XAML, but Avalon encompasses more then just 2D vector graphics. It contains 3D graphics, Printing, Animation, and other graphics goop. XAML doesn't stop with the graphics side. Any .Net component will be able to be express as XAML. So I can create my own component (visual or not) and use XAML to bind it to any other .Net component. Ask the XSmile guys how easy it is to try to get XHTML, SVG, SMIL, CSS, XSLT, XForms, XSL-FO, and X3D to work together, no less some 3rd party API. The Object models behind these W3C created languages were never designed to work with each other, and the W3C has been extremely slow to respond to this need.
----- 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/
