@Ross
The more and more we all talk about this, and I get to see examples,
the more I would like to see a working example of yours.
I really like the simplicity and flow of your idea and with your
permission, like to try out your style of MVC based off your example.
My idea is to leverage
+1 !!!
Oh, would I love to see this too!!
Best regards,
Cor van Dooren
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Karl
DeSaulniers
Sent: dinsdag 6 maart 2012 10:26
To: Flash Coders List
Forgive me if I am wrong, but I watched that video and it confused me.
The gentleman started creating the view first then made the model and
had the interaction between the two
then went and created the controller and in creating the controller
took away some code from the view that the
model
My guess is the view needs the reference to the controller, because it
invokes function in there to update the model through the controller.
I am not a OOP or MVC specialist, and know nothing more as showed in the
video, so don't shoot me!
-Original Message-
From:
You could ofcourse take another approach:
In the view:
dispatchEvent(new Event(View.YOURVIEWEVENT));
and in the Contoller:
View.addEventListener(View.YOURVIEWEVENT, callback);
So there is a loose coupling as Paul wrote.
-Original Message-
From:
Bang!
:)
On Mar 6, 2012, at 4:21 AM, Cor wrote:
My guess is the view needs the reference to the controller, because it
invokes function in there to update the model through the controller.
I am not a OOP or MVC specialist, and know nothing more as showed in
the
video, so don't shoot me!
I kind of like that.
I guess I am looking to the controller to do the event dispatching to
the model
the model to listening for the result. the view listening for changes
to the model.
On Mar 6, 2012, at 4:26 AM, Cor wrote:
You could ofcourse take another approach:
In the view:
More like a CMV
Well its bedtime for me. Looking forward to more discussions.
Best,
Karl
On Mar 6, 2012, at 4:35 AM, Karl DeSaulniers wrote:
I kind of like that.
I guess I am looking to the controller to do the event dispatching
to the model
the model to listening for the result. the
On 06/03/2012 10:35, Karl DeSaulniers wrote:
I kind of like that.
I guess I am looking to the controller to do the event dispatching to
the model
The controller manipulates the model, so it wouldn't really need to
dispatch events to it.
the model to listening for the result. the view
I guess I am looking to the controller to do the event dispatching to
the model the model to listening for the result.
You don't normally do that. The controller talks to the model directly, so the
controller knows the model.
The model doesn't know neither view nor controller and dispatches
I think a core concept got lost with MVC - the controller controls
things. That is, it can directly update (control or talk to) a model and
a view.
A model should not directly update (control) anything except it's own
data sources (remote or otherwise), and should only broadcast changes to
Also, this thread has helped to flesh out my understanding of MVC to a
substantial degree. I love that. :-)
Kevin N.
On 3/6/12 11:40 AM, Kevin Newman wrote:
That's how I understand MVC anyway.
___
Flashcoders mailing list
Absolutely agree, so thank you everyone - very much.
Each day I look for more.
As a result of people talking about RobotLegs I bought and today
received Joel Hooks' ActionScript Developers Guide to RobotLegs.
A new direction - which I am thankful for.
John
On 06/03/2012 18:57, Kevin Newman
+1
Best regards,
Cor van Dooren
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of John
McCormack
Sent: dinsdag 6 maart 2012 21:30
To: Flash Coders List
Subject: Re: [Flashcoders] MVC style Correction
14 matches
Mail list logo
