In case of "real" mxml provided by Flex you need create "hard" instance of your swf with certain layout. Client-side swf generation (like Flex 2) requires a number of mxmls (and so a number of swfs) per layout without benefits of changing layouts on-the-fly. Server-side mxml generation does not allow to change layouts on-the-fly and Flex Enterprise Services are not inexpensive solution. Having as2 (as3 in future) library dealing with mxml (or ASML for actionstep) have a lot of benefits (but a lot of questions: performance issues, change layouts on-the-fly issues etc.).
IC> Same to me, I couldn't undrestand that IC> 2005/11/5, Tim Beynart <[EMAIL PROTECTED]>: IC> I am confused... The free Zorn beta plug-in compiles MXML to swf at IC> compile time. Are you using classes to convert MXML at runtime to IC> components? Is so, can you explain the advantage of this? I understand IC> that you are offering this as free open source code, but once Zorn is IC> released as a product it will probably be affordable and very well IC> supported. IC> I don't mean to criticize your effort, I am asking these questions with IC> an open mind and am really curious about your motivation. IC> IC> - - - - - - - - - - - - IC> Tim Beynart IC> Athens, GA, USA IC> - - - - - - - - - - - - IC> _______________________________________________ IC> osflash mailing list IC> [email protected] IC> http://osflash.org/mailman/listinfo/osflash_osflash.org -- Best regards, Constantiner mailto:[EMAIL PROTECTED] _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
