http://bie.no/blog/computers/software-engineering/actionscript/2007/01/getting-started-with-cairngorm/

On 5/10/07, Dimitrios Gianninas <[EMAIL PROTECTED]>
wrote:

  First make sure u have build simple Flex apps and understand the little
things about Flex.

Secondly, read the 6 page article by Stephen to understand what Cairngorm
is and how it works. Dont worry about version numbers, v0.99 and v2.1 and
almost identical. It is a micro-architecture, it is so small and simple.
Then start a small Flex app that will use Cairngorm, create a View, a Model,
a Command, a Delegate put it all together, run it and then watch it all
work. If you keep it simple you should get the hang of it pretty fast.

Enjoy!

Dimitrios Gianninas
Optimal Payments Inc.

-----Original Message-----
From: [email protected] <flexcoders%40yahoogroups.com> on behalf
of Nate Pearson
Sent: Wed 5/9/2007 2:28 PM
To: [email protected] <flexcoders%40yahoogroups.com>
Subject: [flexcoders] How to learn Caringorm

IN SHORT:
What is the best way to learn Caringorm?

IN LONG:
I want to learn Caringorm. I only make flex apps internally for my
company. My "problem" is that everyone loves flex; I would call it
scope creep but it's more like scope run. The bigger the apps get,
the more visible they are and the more people want them.

I am sold on the Caringorm method of separating things out and making
it very modular. I am excited about learning it and I think it will
make my more productive.

Now my problem is the learning curve. I have visited
caringormdocs.org. The first thing on the list is the six-part
article from adobe consulting. I've read the first part and it raises
my concerns when it talks about the upcoming release of flex 2 and it
references Caringorm .99 (it's on 2.1 now!). I have 0 experience with
Flex before version 2 and I'm afraid that learning an older version of
the framework might hinder my development.

The other two learning tools that they list are the Caringorm Diagram
and the Caringorm Diagram Explorer. Now in theory I understand what
is going on. In practice these diagrams don't help me implement the
Caringorm framework. I feel they are geared more towards people who
already have a good foundation.

My third option is the examples. This is my next plan of attack, I'm
going to go after the basic example and try to duplicate it in a
project that I'm working on.

So community; what do you guys think is the best way to learn Caringorm?

--
WARNING
-------
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.

AVIS IMPORTANT
--------------
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.




--
André Rodrigues Pena

LOCUS
www.locus.com.br

Blog
www.techbreak.org

Reply via email to