RE: [flexcoders] Cairngorm architecture question

2007-12-14 Thread Dimitrios Gianninas 
The Flex framework will create the view cause you are gonna create your various 
views as MXML component and then bind some model data to them. In your case it 
seems like you want to create views on the fly, so when u create them you will 
have to code your binding statement manually in some command.
 
Dimitrios Gianninas
RIA Developer and Team Lead
Optimal Payments Inc.
 



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of Jamie S
Sent: Friday, December 14, 2007 1:42 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Cairngorm architecture question



I've started using Cairngorm for a project and I'm trying to stick
closely with the design philosophy but I'm running into problems.

Here's the situation... My application has to instansiate one of a
number of view classes based on an xml config file. But within the
context of Cairngorm I don't see a good way to dynamically create
views. Right now I'm using the ViewLocator class to refer to a generic
container and having a command create a new view instance as a child
of the container but this seems kludgey and not really in the spirit
of the framework.

The only other thing I can think of is to make my generic container a
little smarter and have it bind to a config data model, creating a
child view once the config data model is populated. But that doesn't
seem quite right to me either.

I guess the main problem is that under Cairngorm, it seems pretty
logical that the Controller/Commands can create and manipulate models,
but what should create views?

Jamie


 

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

RE: [flexcoders] Cairngorm Architecture Question - How to Implement a Workflow

2007-01-03 Thread Dimitrios Gianninas 
Is each view in a Viewstack... so it is as easy as changing the selectedIndex? 
I assume so.
 
So from the command change the index which is in the model like so:
 
ModelLocator.myStackIndex = 2;
 
Then bind that variable to the stack:
 
mx:Viewstack selectedIndex={ModelLocator.myStackIndex}
/mx:Viewstack
 
Dimitrios Gianninas
RIA Developer
Optimal Payments Inc.
 



From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On Behalf Of 
Battershall, Jeff
Sent: Wednesday, January 03, 2007 12:28 PM
To: flexcoders@yahoogroups.com
Subject: [flexcoders] Cairngorm Architecture Question - How to Implement a 
Workflow



I've got an app consisting of several discrete views (MXML components)
performing different admin functions.

One of the components has the user submit a form, after which I'm going
to have the user review the results before finalizing (approving) the
submission.

I'm interested in anyone's feedback on the best way to approach this.
If I fire off a Cairngorm Event/Command to do the submission, how do I
return control back to the view that fired the event after the
submission is complete so that it can perform the next step in the
process (approval)? Seems like a total kludge to pass a reference to the
view with the event I'm firing. It also seems ridiculous to implement
logic at the ModelLocator level. 

Currently, I'm leaning toward having my Command class extend
EventDispatcher and fire off a completion event which is listened for by
the view, which then starts the approval step, which then fires off its
own event/command class. My view needs to respond to the current step
completed - question is the best, cleanest way to implement this.

Jeff Battershall
Application Architect
Dow Jones Indexes
[EMAIL PROTECTED] mailto:jeff.battershall%40dowjones.com 
(609) 520-5637 (p)
(484) 477-9900 (c)


 

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