>> My understanding is that this gets converted to AS3 prior to compilation.
This is true. You could infer some MXML structure based on the AS3 code, but it would be complicated to do. >>. Any Flex programmer will, in fact, know >> AS3 because you can't write a useful Flex app with MXML alone. This is true as well. Not that I am a complete pro at Flex, but I have found you want to know both MXML and Actionscript fairly equally. On large projects, I spend more time in Actionscript, but having the MXML makes life much easier and is important to make use of, MXML can save you a lot of time and headaches. I do think there are uses for MXML that are non-visual though, like setting up a webservice connection, describing effects (which I guess you could argue is visual, but it not a "layout" thing) or even loading XML, but for the most part, I think you're right. MXML for the view - what you see, and Actionscript for most everything else. You can even write arrays and stuff with MXML but I've never seen a good reason for that. Jason Merrill Bank of America Global Learning Shared Services Solutions Development Monthly meetings on the Adobe Flash platform for rich media experiences - join the Bank of America Flash Platform Community _______________________________________________ Flashcoders mailing list [email protected] http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
