Comments on: Piping the Machine: PureMVC Multicore with Pipes and the Finite State Machine (FSM)

By: fellowes_binding_machine

fellowes_binding_machine — Wed, 21 Oct 2009 07:39:39 +0000

This is so interested! Where can I find more like this?

By: Joel Hooks

Joel Hooks — Sun, 19 Jul 2009 00:36:12 +0000

That's awesome Greg. Pipes is really a fantastic tool once you get your head around it. You'll dig the State Machine too. Cheers

By: Greg

Greg — Sat, 18 Jul 2009 19:40:40 +0000

Hi Joel, thank you. I used your example and the one at http://www.tekool.net/ as the basis for an Actionscript only project. I implemented IEventDispatcher in a module data proxy so it can dispatch an event when it is updated. I passed the module facade to each module on instantiation so each module retrieves its proxy and then attaches a listener to it. This also allows the module to directly notify its junction mediator. Each module is assigned to an index in the proxy array. This acts as a data binding to the proxy, something not readily available in Actionscript only projects. Module to module communication is then bounced off the shell back to the intended module index in the proxy. I also modified the module message header to contain a to-module and a from-module parameter. When the module proxy gets an update it uses the to-module parameter as the index in it's array. As mentioned prior each module listens to its index in the proxy. As a side benefit each module can also access another modules data if needed and I suppose an index in the proxy could be assigned to the shell so that data would be readily available too. The next step is to use the state machine for layout control perhaps implementing a three phase process like the Flex Layout Manager does. Thank you again for your great example.

By: Joel Hooks

Joel Hooks — Wed, 15 Jul 2009 14:35:53 +0000

I don't find Pipes difficult ( any more ) and while I have huge respect for Darshan's efforts with Fabrication, it extends virtually every single PureMVC framework creating an entirely new framework. I really like working from the reference PureMVC.

By: grantdavies

grantdavies — Wed, 15 Jul 2009 11:54:21 +0000

Nice example, have you tried the fabrication utility ? It makes pipes considerably easier and removes a lot of the, excuse the pun “plumbing.

Cheers
grant

By: joelhooks

joelhooks — Thu, 09 Jul 2009 19:40:00 +0000

DoodadMediator mediates an individual Doodad (viewComponent) where-as DoodadModuleMediator is mediating the whole module (non-visual). DoodadModuleMediator is instantiated in the Shell and is owned by the ShellFacade.

By: Greg

Greg — Thu, 09 Jul 2009 18:34:07 +0000

First of all, thank you for the example.
I have a question though. In AddNewDoodadCommand doesn't DoodadModuleMediator take the Doodad as its parameter?
I am unable to work past this. Thank you.

var doodadModuleMediator:DoodadModuleMediator = new DoodadModuleMediator( doodadModule );

public function DoodadMediator(viewComponent:Doodad)?

By: anton mejorada

anton mejorada — Sun, 31 May 2009 12:36:21 +0000

Thanks for the clear description. Im a little less scared now after reading your post.

Would this be a realistic framework to use if I have a bunch of individual modules or widgets (8-9 displayed at one time), which must synchronize with each other based on event(s)? For example, clicking on one frame displayed on the shell, would affect another window(s) display. Would I be using the pipes in this instance?

It seems that pipes send messages from a module to the shell, and then vice versa, but would they be used to send messages from one module to many other modules? If so, would you have a spaghetti path of pipes between the modules being displayed? Thanks again.

By: Alex

Alex — Fri, 29 May 2009 06:41:01 +0000

Thanks a lot! It realy helps.
Does anybody know anything about PureMVC multicore port for Objective-C?

By: neil manuell

neil manuell — Thu, 28 May 2009 09:18:42 +0000

this is cool. someday soon I’m going to have to use piping, and this is where I’m going to start