Skip navigation

As FITC came and went at the end of April, the original developer for PureMVC Cliff Hall could not make it (sprained ankle), but Tim Willison covered for him. He posted some slides at his blog in regards to PureMVC development. He provides an example done in Flash. (I assume it to be in Flash CS4. Most examples are done in Flex. So this is a treat!)

Here are the links:

FITC: http://www.oddlystudios.com/?page_id=192&paged=3

Example, Part 1, 2, 3: http://www.oddlystudios.com/?page_id=192&paged=2

Part 4, 5, 6: http://www.oddlystudios.com/?page_id=192

DJ

3 Comments

  1. Hi David,

    Nice example and tutorial. However, everyone has their own conventions and ways on how to use the framework. I also noticed that some very important functionalities are missing from the framework included in the example: e.g. the “onRegister” and “onRemove” public API functions for the mediator. This must be an older version. Here are some of the things I prefer to do when using the PureMVC framework:

    1) Instead of overriding the getMediatorName() function, you just pass the NAME constant in your call to the parent class: super(NAME, viewComponent)

    2) Add your listener in the overriden “onRegister” function and remove them in the “onRemove” function. This enables you easily swap the mediator at run time if needs be.

    3) I tend not to put my notification constants in the ApplicationFacade. I instead try to put them in an enumeration class. This way, you prevent the thight coupling between the mediators and the facade. So, I create one class, let say “ProjectNotifications” and put all of my primary notifications in there.

    4) I prefer using the name “view” instead of “asset”. I think it fits better with the concept MVC but this is definitely my own preference.

    Yves

    P.S. I really look forward working with you guys. Hope it will happen soon.

  2. Hey David, Whyves,
    Yep, it is the older Singleton version of the framework in the example. I still like to use that one to introduce people to the framework. So onRegister is not really in use, as this became important with Multicore (and in fact you MUST add your listeners in onRegister now, or set it up to have a command hit the Mediator’s pulic API at the right time). I do like an enumerator class as well, but I find I use them less with multicore, as most of the cores do not have a large number of notification constants – they tend to be smaller, less complex, and broken up into modules.
    I have a couple of newer examples of multicore and pipes to go up on the site, I’m just polishing them and writing supplementary notes. I could not find good examples of non-flex use of this utility, so perhaps you might find them interesting to look at.
    -timbot

  3. Thanks guys for the comments! 😀


Leave a Reply

Your email address will not be published. Required fields are marked *