View Component Library - Mediators go where?

[mark_ellul]

Hi,

I am new to PureMVC.

I am creating a System, where I want a few view components to be in a library which would be shared across a few applications ... for example an ATOM feed viewer.

Would I put the Mediator in each Application for this ATOM Feed viewer? How would I bind my view to the ATOM feed if each Application has its own Model?

I hope I have made myself clear, any help would be appreciated

Regards

Mark

[mark_ellul]

I have been thinking about it... and It almost makes sense to have A Mediator in the Component library that can be inherited from in each application, to say handle the clicking on each article to do different things.

Does that make sense?

 About the Model,  I am still a little confused... would I just use an variable in my component and use the inherited Mediators to get the value from the Proxy??

Regards

Mark

[trilec]

Hi Mark,
Being new to this, I dont want to lead you down a strange path.
however, Have you consided the multicore version.
your AtomReaderWidget would be loaded as its own app within you main App.
The multicore framework can also unload and load other widgets you may have.
checkout Modularity demo.
A point Cliff made was that you would need to create interfaces for each core to talk to the surrounding app and for that app to talk to the other cores.

http://trac.puremvc.org/Demo_AS3_MultiCore_Flex_Modularity

T

[mark_ellul]

HI T,

How stable is the Multicore Port of the Framework?

I like the idea of loading the widget at run time... 

Regards

Mark

[trilec]

Hi Mark,
 It's using much of the same core as the standard vision, just with additional functionality for the multicore list , it has not been unit tested but Cliff feels it's reasonably stable.

T

[puremvc]

Mark,

The.MultiCore version is still 'experimental' because I haven't yet had the chance to port the unit tests. It has all the same functionality as the standard version and. Knowing the changes I had to mak I feel very confident. But feeling confident and seeing the green bar in FlexUnit are 2 different things, thus the current status

I definitely encourage you to spend a little time with it if you have a problem that would best be handled with modules.

However, to see how to package and reuse a utility such as you describe, have a look at the AIR utility called DesktopCitizen and its related demos.

-=Cliff>