PureMVC : Lazily Instantiated Components

One small caveat when working with PureMVC – If your View object is defined at design time, but not created at application startup you’ll need to defer the

facade.registerMediator( )

Joshua Ostrom wrote a nice little piece about this.

Check it out…


PureMVC & Cairngorm : Introducing Tech Per

Tech Per had visited my blog yesterday, just to find a spurious blog entry of unknown origin on which he diligently commented and asked if “I was serious”, however using different wording.
Nevertheless, I promptly deleted the post and went to Mr. Per Tech’s website to find a way to offer an explanation as he was absolutely right, I was not serious and I still have no idea how the entry had arrived on my blog (I stand to blame an empty bottle of cognac, but I still don’t have concrete evidence – only circumstantial).

Nevertheless, and all other things being equal…
Per Tech has an interesting blog and I suggest all to pay it a visit.
One post on his blog, to which I have dedicated this entry, is about PureMVC and Cairngorm. The post is just some arbitrary thoughts from Per Tech on the topic, and its quite liberating to read some simple thoughts… and not read something which the author had probably envisioned as being the final breakdown of differences offering complete closure to all disputes and provide objective and unbiased precedence for years to come… These are just ideas, and as such needs no more introduction…

Check it out…


State Machines : The C in PureMVC

I have some difficulty figurering out how to combine the notion of a statemachine workflow with the PureMVC notion of commands as the primary work-units. Using states seems to defy the need for commands and if not in direct conflict only because one could imagine using the statechange events to trigger commands. However, the ladder seems to create additional complexity in return of no other benefit than being able to use a statemachine workflow as the primary driver in a strict PureMVC system without removing logic from the commands.

Cliff Hall started a working group with this focus, but it appears that they too have had some difficulty cornering the right way to combine this.

Check it out…


PureMVC : Pipes and intermodular communications

The PureMVC team (Read ‘Cliff Hall’) has been working this week on a new utility called Pipes. Its being unit tested right now and they expect to put up a demo soon.
Pipes will henceforth be the main way that modules communicate without having references to each other or sharing a Facade… very cool stuff.

Check it out…


Pretty printed source

Adobe Flex

PureMVC & Cairngorm (1)

We have recently been blessed with a couple of very skilled PureMVC oriented developers. Seeing that we have traditionally been a distinctive Cairngorm company, this was naturally an issue we needed to address… however, upon considering the options we came to the conclusion that there were no apparent reasons why our specific implementation of the Cairngorm framework could not coexist happily side-by-side with PureMVC. A number of apparent conflicts based on the various singleton’s would have to be solved, but seeing that we have abandoned the singleton FrontController’s and ModelLocator’s in both frameworks all we had to do was to hook the PureMVC Facade and our custom Cairngorm EventBroadcaster together so our events being dispatched in one place will be delegated to the other place.
What we eventually end up with is a Hybrid which is based on Cairngorm but 100% faciliates PureMVC-based code and it seems to work without any major issues.

This is the first of what will become a number of posts I will be making about our experiences in taking a 1300+ Class large system based on Cairngorm and adding PureMVC to it.