RE: [Flashcoders] MVC style Correction
Models shouldn't have any knowledge of each other or anything outside of themselves. The controller should usually be the first area to set up. Everything else is set up and managed by the controller (views, models, services). Usually, there will be one central controller that handles your main program management. Other controllers can be set up and delegated by the main controller, but this is not always necessary. In a well set up MVC application, Models and Views don't talk to each other. Rather, they let the controller carry out that communication. jord Original Message Subject: Re: [Flashcoders] MVC style Correction From: John McCormack Date: Sat, February 18, 2012 1:22 pm To: Flash Coders List A really nice explanation. I tried to find your EastAsMVC after being on your site, is it on the way? Also, what comes first, ie. how do the models, controller and Views find out about each other? Does everything register with the (single) controller? John ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Fwd: MVC
(UGH... I hate RTF Web editors) RobotLegs is not a big framework at all. In comparison with most of the other frameworks out there, it's overhead is far far less than ones like Cairngorm, Spring and Parsley. Even compared to Mate and SWIZ (which are very small to begin with), then RobotLegs is lighter at 47K overhead. 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 and Models shouldn't care who's using them (Controllers are just conduits between Views and Models). On a larger scale, this would present itself to be a huge maintenance nightmare and dependencies have now been created. Everything should be independent of each other enough that I could replace one section without affecting the operation of anything else in the application. In this case. the controller should be passing either Value or Transfer Objects back and forth between the View and Model. This way, I could change models on the fly and the controller and view wouldn't suspect a thing. RobotLegs is an excellent example for learning about MVC. jord Original Message Subject: RE: [Flashcoders] Fwd: MVC From: "Cor" Date: Thu, February 16, 2012 8:39 am To: "'Flash Coders List'" Ross, And you did get people started. At least me! I am also very interested in your fuller framework. I don't wish to use the big frameworks as RobotLegs, etc. I want to learn to create good MVC from scratch. Best regards, Cor van Dooren -Original Message- From: flashcoders-boun...@chattyfig.figleaf.com [mailto:flashcoders-boun...@chattyfig.figleaf.com] On Behalf Of Ross Sclafani Sent: donderdag 16 februari 2012 14:28 To: Flash Coders List Subject: Re: [Flashcoders] Fwd: MVC I have a fuller framework that details a view life cycle, subModels, a Controller tree, animated transitions on change() and more. The classes I wrote are just the simplest examples that I thought would get people started. I'll get the framework polished up and open sourced to Github if you guys are interested Ross P. Sclafani Owner / Creative Director Neuromantic Industries http://www.neuromantic.com http://ross.sclafani.net http://www.twitter.com/rosssclafani 347.204.5714 ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Fwd: MVC
___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Question about SWC elements for use in Flex
If you don't need to use Flex, then it's all good. However, if Flex is required, it's not really an arduous task to create a wrapper. We do this this for various sprites developed in FLA's to maintain reuseability throughout. jord Original Message Subject: Re: [Flashcoders] Question about SWC elements for use in Flex From: "Eric E. Dolecki" Date: Wed, September 21, 2011 1:24 pm To: Flash Coders List Thanks for your response. I have to weigh whether or not I want to jump through the extra hoop or not (I can create a non-MXML app where I can do things straight away). Thanks again, Eric ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Question about SWC elements for use in Flex
(I hate webmail apps... resent) addElement() is meant for display objects that extend the SpriteVisualElement class, which are a part of the Flex libraries. What you need to do if you want to use Sphere as you have made it, is to create a wrapper display object that extends SpriteVisualElement and have the wrapper add your Sphere object via an addChild(). You would do an addElement() on your wrapper. jord Original Message Subject: Re: [Flashcoders] Question about SWC elements for use in Flex From: "Eric E. Dolecki" Date: Wed, September 21, 2011 11:04 am To: Flash Coders List If I make an ActionScript Project - things work fine. I link the SWC, import the asset's stub class & I can use it. However I can't figure how to do the same for a Flex Project or Flex Mobile Project yet. ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
RE: [Flashcoders] Question about SWC elements for use in Flex
___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
