RE: [flexcoders] Theory and Practice: Mixing AS2.0 in MXML

[Dimitrios Gianninas]

DataBinding is definitely one 
of the high points of Flex and is used very often in our first Flex 
implementation here at Optimal. I see no need to stop using a feature that helps 
make development easier and quicker. 
 
We are now creating prototype 
Flex UIs for 3 other projects, none of these UIs are functional, they are mostly 
screen mock ups. However one of the first things we do is use data binding to 
say connect a DataGrid to a form to show end-users what the final product might 
do, so in this case data binding is easily and quickly used for 
prototyping minimal functionality in a UI.
 
As for the "don't ever include 
AS2 code in MXML ever", well I have to agree with Steven on that one. As I 
browse through my MXML code, 65% of the MXML files don't contain AS2 code 
at all, however the other 35% do in some small fashion because it didn't 
warrant a full blown AS2 class to implement 2-3 lines of AS2 code to do 
something. Like Steven said, I pretty much think this decision is leftup 
to the developer as to how much AS2 code to leave in a MXML file and when it is 
time to re-factor it into an AS2 class.
 
Jimmy 
Gianninas
Software Developer - 
Optimal Payments 
Inc.
 


From: Steven Webster 
[mailto:[EMAIL PROTECTED] Sent: Thursday, March 03, 2005 
7:01 AMTo: flexcoders@yahoogroups.comSubject: RE: 
[flexcoders] Theory and Practice: Mixing AS2.0 in MXML
> > 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 ofintroducing > 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 thecontrary, it provides an elegant way of 
expressing an entirely commonrequirement of listening and notifications) nor 
can I understand howdatabinding threatens scalability.I very much 
doubt there are any real-world Flex implementations outthere today, where 
data binding usage is the make or break betweenwhether the app is scalable 
and maintainable or not.Promoting "no ActionScript 2.0 at all in MXML" 
to the wider developmentcommunity, and extending that to include 
data-binding, is something thatmakes me incredibly nervous...and I suspect 
that as well as most real-world implementations having benefited greatly 
from data-binding, the architectsand 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 removingall 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 WebsterTechnical 
Directoriteration::twoThis e-mail and any associated attachments 
transmitted with it may containconfidential information and must not becopied, or disclosed, or used byanyone other than the intended recipient(s). 
If you are not the intendedrecipient(s) please destroy this e-mail, andany 
copies of it, immediately.Please also note that while software systems 
have been used to try to ensurethat this e-mail has been swept for viruses, 
iteration::two do not acceptresponsibility for any damage or loss caused in 
respect of any virusestransmitted by the e-mail. Please ensure your ownchecks are carried outbefore any attachments are opened.

AVIS IMPORTANTWARNING Les informations contenues dans le present document etses pieces jointes sont strictement confidentielles et reservees a l'usagede la (des) personne(s) a qui il est adresse. Si vous n'etes pas le destinataire, soyez avise que toute divulgation, distribution, copie, ou autre utilisation de ces informations est strictement prohibee. Si vous avez recu ce document par erreur, veuillez s'il vous plait communiquer immediatement avec l'expediteur et detruire ce document sans en faire de copie sous quelque forme. The information contained in this document and attachments is confidential and intended only for the person(s) named above. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution, or any other use of the information isstrictly prohibited. If you have received this document by mistake, pleasenotify the sender immediately and destroy this document and attachments without making any copy of any kind.