I second to Cairngorm, though you might want to spend a few days picking it
up unless you are already familiar with MVC.  Even with some of our
developers who are already familiar with MVC, it took them more than 3 days
to get barely comfortable.  The website, http://www.cairgormdocs.org/ has
great workflow and visual documentation.

 

-          Tangent

 

 

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Dimitrios Gianninas
Sent: Thursday, October 25, 2007 11:43 AM
To: [email protected]
Subject: RE: [flexcoders] Components best practices for a newb

 

You are looking for an architecture :) One of the most popular for Flex is
Cairngorm, check it out here: http://labs.adobe.com/wiki/index.php/Cairngorm

 

But yes, you should definily break things out into their own components, the
smaller the better, it will help you manage code, more easily add features
and locate bugs. RemoteObjects as well, if you read the Cairngorm stuff, it
has that already.

 

Dimitrios Gianninas

RIA Developer and Team Lead

Optimal Payments Inc.

 

 

  _____  

From: [email protected] [mailto:[EMAIL PROTECTED] On
Behalf Of Phill B
Sent: Thursday, October 25, 2007 11:25 AM
To: [email protected]
Subject: [flexcoders] Components best practices for a newb

I'm putting together my first Flex app and need some help. I have all
my code in one mxml file and it is getting hard to read. So, I would
like to break out code in to components.

Should I put my remoteObjects in a component?

Should I break out all of my vars as well?

Are there any good tutorials for me to look over for doing this?

Thanks for the help

-- 
Phil


AVIS IMPORTANT

WARNING


Ce message électronique et ses pièces jointes peuvent contenir des
renseignements confidentiels, exclusifs ou légalement privilégiés destinés
au seul usage du destinataire visé. L'expéditeur original ne renonce à aucun
privilège ou à aucun autre droit si le présent message a été transmis
involontairement ou s'il est retransmis sans son autorisation. Si vous
n'êtes pas le destinataire visé du présent message ou si vous l'avez reçu
par erreur, veuillez cesser immédiatement de le lire et le supprimer, ainsi
que toutes ses pièces jointes, de votre système. La lecture, la
distribution, la copie ou tout autre usage du présent message ou de ses
pièces jointes par des personnes autres que le destinataire visé ne sont pas
autorisés et pourraient être illégaux. Si vous avez reçu ce courrier
électronique par erreur, veuillez en aviser l'expéditeur.

This electronic message and its attachments may contain confidential,
proprietary or legally privileged information, which is solely for the use
of the intended recipient. No privilege or other rights are waived by any
unintended transmission or unauthorized retransmission of this message. If
you are not the intended recipient of this message, or if you have received
it in error, you should immediately stop reading this message and delete it
and all attachments from your system. The reading, distribution, copying or
other use of this message or its attachments by unintended recipients is
unauthorized and may be unlawful. If you have received this e-mail in error,
please notify the sender.

 

Reply via email to