> MXML is a piece of crap, mixture of XML and AS code. Very bad overview and > readability.
That's an interesting take on things. For me, I believe the exact opposite - the separation of UI/layout into MXML makes perfect sense, and follows the model used by many other desktop application development environments. UI and layout fits sensibly in a declarative framework, which is what MXML gives you. The only AS you need in your MXML is that for event handlers. Everything else can be extracted into separate AS files quite easily. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ Fig Leaf Software provides the highest caliber vendor-authorized instruction at our training centers in Washington DC, Atlanta, Chicago, Baltimore, Northern Virginia, or on-site at your location. Visit http://training.figleaf.com/ for more information! _______________________________________________ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders