I don't know of any doc anywhere. It is not fixed in Flex 3. I don't expect Thermo to auto-convert the Flash fl.* components into Thermo components either. The designer is really supposed to draw pure bitmaps or vector art and Thermo makes it easier to translate that into Flex apps. If the designer actually puts a fl.* component in the artwork, Thermo may not be able to work with it.
Post Flex 3, there may be some way of using Flex components in Flash Authoring or getting better interop between Flex and fl.* components, but nothing you can bank on and you may not see it until 2009. If someone gave me a Flash CS3 FLA and asked me to re-code it as Flex, I would probably run it in the debugger and write down the size and positions of everything in the display object tree and copy those into the MXML. I haven't used Movie Explorer enough to know if it is a better way of doing that. Assuming there isn't any tricky resizing logic, it would also be possible to write another Flash app that loads the designer's SWF and outputs the appropriate MXML by scanning the display object tree and emitting the XML. ________________________________ From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Justin Winter Sent: Wednesday, January 30, 2008 11:38 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Re: Error #2025 - Clash between Flex 3 (Beta 2) & Flash CS3 (Possible Bug) Alex, Thanks for the quick reply! Is this issue documented anywhere? Is there any workaround you could think of? I'm struck again and again with the same situation where a designer puts together a application shell in flash and rebuilding that design again, piece by piece in Flex is a huge workflow pain! Especially when a layout gets complex. I really hope Thermo lives up to all the hype and that at least the component kit starts to become more than a "flash wrapper". I think "thanksmister.com" says it best in a comment on his blog: "Yeah, its funky right, it like two versions of AS3, and they don't like each other. This mofo problem cost me days and lots of stress. I hope that Flex3 will resolve some of the inconsistencies."
