> > On a similar note, data binding is an immensely powerful > feature of Flex; > > And one that is great for quick-and-dirty hacks and > prototyping but it does not belong in a large-scale application where > maintainability and scalability concerns outweigh the hazards of introducing > such logic into your MXML.
I can't belive that you have reduced data binding to "quick and dirty hacks" and "prototyping" ! I can't understand how databinding threatens maintainability (on the contrary, it provides an elegant way of expressing an entirely common requirement of listening and notifications) nor can I understand how databinding threatens scalability. I very much doubt there are any real-world Flex implementations out there today, where data binding usage is the make or break between whether the app is scalable and maintainable or not. Promoting "no ActionScript 2.0 at all in MXML" to the wider development community, and extending that to include data-binding, is something that makes me incredibly nervous...and I suspect that as well as most real-world implementations having benefited greatly from data-binding, the architects and engineers responsible for these implementations would in no-way consider their deliveries to have been "hacked" or "prototypes". I'd be curious as to what the others who have shipped apps into production with Flex think on this ? Would you advocate removing all data binding from your "large-scale application" before moving into production ? I wouldn't; but I'd be interested to hear other thoughts... Steven -- Steven Webster Technical Director iteration::two This e-mail and any associated attachments transmitted with it may contain confidential information and must not be copied, or disclosed, or used by anyone other than the intended recipient(s). If you are not the intended recipient(s) please destroy this e-mail, and any copies of it, immediately. Please also note that while software systems have been used to try to ensure that this e-mail has been swept for viruses, iteration::two do not accept responsibility for any damage or loss caused in respect of any viruses transmitted by the e-mail. Please ensure your own checks are carried out before any attachments are opened.
