Comments on: Understanding the PureMVC Open Source Framework

By: bertrand

bertrand — Thu, 04 Feb 2010 00:57:01 +0000

i’ve just finished it and it really helps me !

i begin with pureMVC and i’ve just read the 50 pages pdf downloadable on the pureMVC site before.

i find several tutorials and it’s the best for beginners.

thx to take time to write it from france !

By: JCK

JCK — Fri, 22 Jan 2010 23:31:25 +0000

Wrong implementation of singleton pattern:

public static function getInstance():ApplicationFacade
{
return (instance ? instance : new ApplicationFacade()) as ApplicationFacade;
}

You never set instance = new ApplicationFacade(), so the function aways returns new ApplicationFacade()

By: Ted

Ted — Thu, 21 Jan 2010 19:34:25 +0000

Just wanted to say thanks for the tutorial – best one I have seem by a mile. Great to see one from someone with real world experience too.

By: AS3 on PureMVC. Round One. — Joao Pescada (jpscd) | Blog

AS3 on PureMVC. Round One. — Joao Pescada (jpscd) | Blog — Wed, 06 Jan 2010 13:51:59 +0000

[...] bare fundamentals, you’ll soon be flying your way around it.” — Ahmed Nuaman said it on the first tutorial on PureMVC I’ve read, and I could not agree more (though I’m still learning the flying [...]

By: swati chavhan

swati chavhan — Wed, 06 Jan 2010 06:13:01 +0000

hi ,

I am new to puremvc pls can you tell me which tutorial to refer because i am not able to understand what you have explained.

thanks

By: agitcraft » A Solution to the No-Design Cycle

agitcraft » A Solution to the No-Design Cycle — Tue, 05 Jan 2010 20:58:05 +0000

[...] working in PureMVC, you can download the AS3 port, check out the full API documentation, and follow the tutorial I used to get started learning the framework, courtesy of Ahmed Nuaman. Categories: API • Flash [...]

By: sideDoor

sideDoor — Tue, 05 Jan 2010 07:15:51 +0000

Ahmed, thank you very much for your work on this tutorial!

@Kris:

Agreed: in the case of the model, the constants used to denote dispatched events should belong to the model; the model should not “peer” into the view to use its static constants to dispatch events…

By: Kris

Kris — Thu, 24 Dec 2009 14:11:26 +0000

Thank you Ahmed for a tutorial that clearly explains the concepts around PureMVC. I am quite familiar with the MVC patterns though, and there is something in your tutorial I find slightly ….em…counter-MVC. I hope you read this comment and take the time to respond.

It seems to me that you are coupling the view and the model quite tightly. With MVC, one of the most important principles (my opinion, of course, but I do think it is a common one) is the separation of the model. So much so that you should be able to take your model components, as they are, and build a completely different view on top of them, with completely different functionality (e.g. end-user vs admin console).

In your tutorial, you have twice coupled the view to the model: once with the notification constants, and then again when you load the images from the actual view (never mind from the mediator, but from inside the ImagesView component!).

I don’t mean to be critical, but I would like to understand your reasons for this approach.

Thanks again for the tut. The best one I’ve read so far

By: jhirm

jhirm — Tue, 22 Dec 2009 15:37:30 +0000

I’d like to briefly respond to the comments questioning the usefulness of using a framework (MVC or otherwise). It’s true that for small projects, using a framework like PureMVC might do nothing but add a lot of extra coding. If you’re building flash banner ads, creating small animations that fit within an HTML site, or doing strictly timeline-based animating, then using a framework like PureMVC is clearly not the answer. But as soon as you start creating sites that are even slightly more involved – dealing with any type of media-rich or content-rich flash sites, for instance, or sites that are updated with new content frequently, or sites which will have frequent (or even infrequent) design changes but keep the same data structure – using a framework quickly becomes a huge advantage. Because the MVC design pattern, when used correctly, does an excellent job of separating the various layers of the application, adding or removing a new feature becomes an easy task. Changing the way a view component looks is simple, and doesn’t need to involve any modifications to the rest of the site. Switching from XML driven content to some type of database connection requires only a few changes within the appropriate model classes (proxies in PMVC).

Though at first the MVC concepts (and to a lesser extent the concepts of OOP) are hard to wrap one’s head around, they’re worth studying. As anyone who’s worked in web design/development for a while knows, project “scope creep” is not just a possibility, it’s an inevitability. Using a framework allows you to easily and quickly adapt to your clients’ new requests, and reduces the headache of adding features, making changes to the design, or modifying the content structure.

I’d also like to thank the author for a fantastic and practical tutorial! It’s really helpful for all of us!

By: Jed

Jed — Tue, 15 Dec 2009 17:00:56 +0000

initializeController is called in the initializeFacade method of the Facade class (which your Applicationfacade class should extend). initializeFacade itself is called by Facade’s constructor.