I have found a way to create the application wide Facade Singleton as well as the Model, View and Controller Singletons.

I am going to draw up the new package structure asap, when this is completed i can begin a new Python port.

As opposed to just modifying the code we need to build from new perspective, avoiding the circular imports.

In puremvc everything knows of the facade and vice versa! How can we provide the same functionaltiy in python?

There is a circular import in the facade / notification area which unfortunately cannot be avoided.

The python port cannot simply be a modified version of the code, it needs to be completely re-designed into a python structure.

I will have a look at some options and see if i can find a new solution for the python port.

I understand where the responsibilities should be divided, I was just wondering what you thought about his approach!

Thanks anyway.

You are passing an array, not the File() Object..

sendNotification( ApplicationFacade.IMPORT_FILE_SELECTED, event.target );

NOT

sendNotification( ApplicationFacade.IMPORT_FILE_SELECTED, [ event.target ] );

otherwise you would have to use note.getBody()[0]

How and what was the "fileSelected" method listening to?

*Bump*

I have the Python port in a working state, i will upload asap.

This problem was pretty easy to fix.

Using "from x import y" is correct, you should not import the whole module. Just avoid circular imports, they usually indicate bad design / structure anyway.

I am very familiar with WxPython and willing to help!

As for the singletons Nathan are you familiar with the "Borg" pattern?

http://wiki.tobydehavilland.com/borg-pattern

Hi Cliff,

David Knape did a presentation on PureMVC using a Gallery application he had built.

In this application he uses a Proxy to store Stage logic such as the Stage "resize" event along with the scale and align properties etc. I would have considered a StageMediator to be the correct place for this logic.

He also retrieves the Stage object from the Proxy and calls its update() method, I can't help but feel that he should have dispatched a STAGE_UPDATE notification instead of gaining reference to the Stage object?

What are your thoughts to his approach? Does the Stage need a Proxy?

Source is available here: http://bumpslide.com/blog/2008/01/16/puremvc_demo_src/

The second option is pretty much correct.

Make your own RPC DAO Class, or use the Flex HttpService etc then your Proxy uses that class to interact with the back end.

Your Commands do not need to interact with any DAO.

Thanks cliff im glad you said that, it is what i had done before i asked the question... I wasn't sure if throwing children around in Notifications was a good idea!

Just a thought... if i dispatch a notification that the stagemediator accepts, why dont i just call a method like addSprite() directly on the mediator? example:

var stageMediator:StageMediator = facade.retrieveMediator(StageMediator.NAME)
stageMediator.addSprite(myChild)

Why would you prefer to use Notifications over this method?

Also... what if the child doesn't need to be added to the Stage, but to another child? For example if i wanted to add a ProductSearchResultView to a ProductPage

Should these be handled by notifications as well? Or by retrieving the mediator and adding it directly to the view component / using a mediator method?

Many Thanks

Also the HelloFlash example does not demonstrate the removal of view components / mediators.

Hi Cliff thanks for the reply.

I have studied all the demos in great detail and unfortunately the HelloFlash example does not really work in my situation because i am building a website which contains many different views that load at different times.

If i was to use the same method as HelloFlash then stage mediator would contain a STAGE_ADD_SOMETHING for every "page" which would get very bloated.