Thanks for your suggestion Dimitrios...
I had thought of that too but
in the MVC architecture, doesn't that
put logic into the view? My impression
of the architecture is that you
should be able to create a different view
over the same model without
duplicating code. I mean, I don't want to have
another view and am
more or less positive I never will but looking at it from
a purist's
point of view is this the 'correct' way to do it?
I suppose
if the rules that you validate against are kept within the
model ie. min and
max allowable responses for the current question in
my case then your
suggestion would be the 'correct' way of doing it.
I think I will go with
your suggestion but I would be interested to
hear if you, or anyone else had
any further opinions...
Thanks again...
Graham
--- In [EMAIL PROTECTED]ups.com,
"Dimitrios Gianninas"
<dimitrios.giannina[EMAIL PROTECTED]>
wrote:
>
> Put a method to handle the validation of the form or
forms in the
view. Then when the user presses the button, validate the
form(s) and
if all is ok then fire the event that calls your command to
do
whatever you want.
>
> Dimitrios Gianninas
> RIA
Developer
> Optimal Payments Inc.
>
>
>
________________________________
>
> From: [EMAIL PROTECTED]ups.com
[mailto:[EMAIL PROTECTED]ups.com]
On
Behalf Of grahampengelly
> Sent: Thursday, September 07, 2006 8:41
AM
> To: [EMAIL PROTECTED]ups.com
>
Subject: [flexcoders] Cairngorm... Where should this go?
>
>
>
> Hi
>
> I am building an assessment application
with Cairngorm. All is going
> swimmingly but I am wondering where I
should put the following.
>
> The view collects the respondents
answers and fires off an event,
> containing them. The Controller picks
this up and updates the Model...
> Pretty standard stuff.
>
>
My problem is that I need to validate the number of answers given. I'm
>
new to the MVC pattern so I am not sure where this should go on. I
> want
to give an alert or something like that to the user if the
> answers
aren't valid. Should I just create the alert in the command
> that lives
in the controller? This doesn't really seem right. Should I
> raise an
event from the model and subscribe to this in the view. This
> seems more
in keeping with what I perceive the roles of each aspect of
> the
architecture to be but seems a bit convoluted.
>
> At the end of
the day I can get it to work in either of these and
> probably a few other
ways but as I have embarked on this architecture
> I would like to make
sure that I am doing it 'properly'...
>
> Thanks in
advance...
>
> Graham
>
>
>
>
>
> --
> 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.
>
|
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.
|
