Jord,
This is exactly what I don't understand to do in actionscript!
And that's why I think some example will visualize it to me.
So I can analyze the flow of it all.
Feel free to contact me offlist if you prefer.
Best regards,
Cor van Dooren
-Original Message-
From:
maybe this will help:
http://www.robotlegs.org/diagram/
the solid lines are method calls, the dashed lines are events
On 17 February 2012 18:58, Cor c...@chello.nl wrote:
Jord,
This is exactly what I don't understand to do in actionscript!
And that's why I think some example will visualize
Hi,
I think you need to set the soundTransform of the MovieClip that
contains the timeline sound?
Also look at the SoundMixer class for global controls - you may need
the stopAll functionality when you add and remove MC's with sound
to/from the stage.
Glen
On 16/02/2012 19:48, natalia
Thank you!
Another piece of the puzzle is filled in.
Best regards,
Cor van Dooren
-Original Message-
From: flashcoders-boun...@chattyfig.figleaf.com
[mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ben Sand
Sent: vrijdag 17 februari 2012 10:11
To: Flash Coders List
Main problem that I see with the code that was posted is that it breaks
a major MVC rule and teaches a real bad habit: Views shouldn't have any
knowledge of Models
Not sure where you get the idea that a View shouldn't communictate with the
Model directly:
This states otherwise:
I'm firmly against views treating models as anything but read only.
Personal preference I guess
Ross P. Sclafani
Owner / Creative Director
Neuromantic Industries
http://www.neuromantic.com
http://ross.sclafani.net
http://www.twitter.com/rosssclafani
347.204.5714
On Feb 17, 2012, at 1:11 PM,
That is a great picture.
Does a controller know an instance of a model?
Orr does the model register with the controller as a subscriber for
specific data changes or events?
Most of all, I wonder how all the parts gets to know each other.
John
On 17/02/2012 09:11, Ben Sand wrote:
maybe
This is particular to RobotLegs.
RobotLegs links a lot of the components in the Context* and then handles
dependency injection.
Other MVC frameworks may have different approaches, here's a good
comparison of Flash MVC frameworks:
Hands down the best explanation of MVC I've ever seen anywhere, is in
this iTunes U series (item 43 at the bottom of the list) - you can just
grab the slides too, but you'll miss all the emotion and humor of the
delivery :-)
I just rewatched the video, and it turns out that I forgot about the
more complicated version with data sources.
But still, if I got it right, the general idea is the controller adjusts
the data into the generic formats for generic views (either all at once
if you skip the data source glue,
Can somebody show me a View class that doesn't update itself? What does it do?
Are all of its properties public?
Conversely, can someone show me a controller class that does the work of both
modifying the model and manipulating the view? Does it lead to a ton of code in
one class?
I'm not
That idea that the one thing MVC interpretations have in common - that
models can only be updated by the controller makes sense.
I tried to learn MVC a few times before it really stuck in my head.
These where the problems I encountered:
- What does MVC apply to? Is it an application level
12 matches
Mail list logo
