> On Wednesday 19 Sep 2007, [EMAIL PROTECTED] wrote: > > As far as I know, Flex gods from Scotland do not advise the use of > > code behind approach as seen in .net. > > It'd be interesting to see that advice :-)
You just saw it :) > > > First of all there is no code generator that would create references > > to all mxml elements in the accompanying AS class. > > So ? > It really doesn't take that long, and no one is suggesting all existing code > is rewritten to code behind. > Besides a 'code generator' is only an Eclipse plugin away. It's not a point in how long it takes, it's just not meant to be used like that. If it would be, there'd be mechanisms to do that. It does seem tempting and I also wanted to do that in the beginning as I wanted clear separation between code and mxml (as seen in .net). But quite soon I realized that it does take a lot of time, more space for errors, not refactoring friendly, etc. Before we got into Flex we even developed our own similar approach with Flash / XML that used code behind, that is, every XML file had accompanying AS class. > > Second and more important, you can't use data binding that way which > > is one of the most powerful features of Flex. > > Eh ? > We use data binding with code behind all the time. It's fine. You can use it of course, but not in the way you would use with code in mxml. It requires more fiddling. > > And there is also third, which is Cairngorm. Cairngorm is ment to use > > mxmls as classes, so you treat them as a class. There's more to > > Cairngorm than this of course but if you'd like to implement it don't > > use code behind approach. > > WTF ?!? > We also use Cairngorm with code behind all the time (not ViewLocator though). > It works fine. > There is no difference between MXML and AS classes, once compiled. It's not after they are compiled, the difference as I see it, is in the development and organizational approach. Cairngorm never advocates code behind. Of course you can implement similar architecture with all the patterns, but Cairngorm is not purely about patterns but also how you organize the project, classes, views, etc. I'm almost convinced that code in mxml is better solution than code behind, though it does seem clumsy at times. > Tom Chiverton > Helping to centrally strategize real-time information > on: http://thefalken.livejournal.com > > **************************************************** > > This email is sent for and on behalf of Halliwells LLP. > > Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at St James's Court Brown Street Manchester M2 2JF. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by the Law Society. > > CONFIDENTIALITY > > This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 8008. > > For more information about Halliwells LLP visit www.halliwells.com. >
