On 7/16/07, dave <[EMAIL PROTECTED]> wrote: > > How would one compare Flex functionality with say, SVG > functionality? This was the context behind my > question. >
nothing to compare really SVG is rendered within the HTML DOM pros: it integrate better cons: it's slow (XAML got the same flaw imho) MXML is the markup representation of the whole UI, no runtime interpretation is done (it's a render), MXML -translated to-> UI structure (not a DOM) -compiled to-> bytecode (and then bytecode-rendered to-> GUI) pros: light to store, very fast cons: less maleable because it's a binary format and not a text format this final bytecode is not re-interpreted (but can be re-rendered), it's a hell lot more efficient and faster (sure you can make dynamic parts similar to a DOM using states, bitmapdata, the drawing API, etc. but the UI structure itself is not a full DOM) as I see it (and it's just my small opinion) a DOM is made to be manipulated at runtime, it allow you to manipulate the document playing on its "nodes" the flash UI structure is more OO, better for my taste :), you got almost the best of the both world: speed and ligthweight storage of the UI definition in bytecode, but also way to manipulate this UI not like a DOM but like a .. logic structure. (ok here I surely expressed it badly) comparing them point by point is not that usefull imho, they both serve different purpose and use in the end why you would choose SVG over SWF or the inverse ? think about something as google map, what it could do more using SVG (and less) ? what it could do more using Flash (and less too) ? could it do everything coders can think of if for ex inside AIR you could layer the SVG graphic data and flash ? but anyway SVG is kind of dead... cheers, zwetan _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
