Yes, of course, Popup doesn't save data directly - it saves it via Proxy

Hello PureMVC forum,

One of our projects has a sort of this mechanism (let's call it 'command as a proxy handler') which works as follows.

E.g., we have an application with a popup and sort of a logging system. The popup saves data using remote method and after result is retrieved it launches some Notification (ProxyResult). We also have a Command (the name is not correct because it doesn't represent any actions - ProxyResultCommand) that closes that popup and sends a success message to the logger.

The alternative approach (and a classic I guess) is to listen that Notification in Mediator that manages popup and the Mediator.

What is the best solution? What to apply if we have a set of actions (close popup 1, close popup 2, send something to Logger). If this can be used what is the best name for this Command?

Pureclipse 1.5 is available.
Details here: http://slide.name/pureclipse

Pureclipse is one of them: http://forums.puremvc.org/index.php?topic=1805.0

SlideUI recently released their development tool called Pureclipse which is a great helper in PureMVC development.
It can be downloaded here: http://www.slide.name/pureclipse/
Currently it supports AS3 only.

Here is a small demo: www.slide.name/styledmodule.fxp

Thanks for the fast reply Rafal. Updating to 0.7.3.1 doesn't help and I can't check the Flex 4.0 version because this app doesn't work well with this sdk.

Flex SDK 4.1 and fabrication-0.7.3-flex.swc is used.
Also, Spark group is used as a container (scm.mainDisplay.search) for the FlexModuleLoader

Hello Fabrication users!

There is a shell application here with a module that is loaded with FlexModuleLoader
Earlier (before I figured out that Fabrication is now supported again) this module was loaded using default <ModuleLoader> component and everything works good. The problem now is that application style is not used in the module loaded with FlexModuleLoader now. There is a number of assets including font styles and images and they are not appled now. The loader is now created in command and then it is added to a container:

:

private function onModuleReady(e:ModuleEvent):void
{
trace('LoadSearchModuleCommand:onModuleReady');
var scm : SectionContainerMediator = SectionContainerMediator(facade.retrieveMediator(SectionContainerMediator.NAME))
scm.mainDisplay.search.addElement(FlexModuleLoader(e.target));
}

It is very sad, that Fabrication is not supported anymore. Hope someone with the right skills and knowledge will continue the good thing.

Seems that retrieveProxy is not accessible from FabricationProxy. Is that done intentionally?
The workaround is to use facade.retrieveProxy instead.

Hello, forum!

There is a main display View with a ViewStack where ListView and DetailView is put. When user hits the item in ListView, ListViewMediator generates a notification that is handled by MainDisplayMediator and it changes the selectedIndex in the ViewStack. The question is how to pass a parameter from ListView (selectedItem) to the DetailViewMediator? What is the best way to do that?

I guess, I need to pass the selectedItem as a notification's argument but the problem is how to pass it further to the DetailViewMediator. Should it be the special Proxy for that?

EDIT:
I found something similar in CafeTownsend demo: there is also a list of employees and a detail screen. But there is a ViewStack with creationPolicy="all" there which simplifies things a lot. A mediator in detailviewmediator just listens to the notification that is generated when list item is changed. In my case I have no mediator at that very moment when List item is changed. So I need register a mediator for the detail when user goes to the details screen. And after that get the value from ListViewMediator.

Thanks a lot,
Mikhail

Amazing how natural PureMVC handles flashvars here! Thanks a lot, Cliff!

Hello,

I would like to know where do you usually place such classes as extended Notifications or class of constants for a specific View Component. Should they fall into model or view directories or they shouldn't be littered with these classes?

Hello

I'm trying to understand why add child resolver doesn't work for me and got the following issue:
I've changed the demo so item is added to the panel and not to the form.

:

<mx:AddChild relativeTo="{loginPanel}" position="before">
                <mx:target>
                <!-- This is where the confirm component is defined -->
                    <mx:FormItem id="confirm" label="Confirm:">
                        <mx:TextInput/> 
                    </mx:FormItem>
                </mx:target>
            </mx:AddChild>After that change the onRegister method of ConfirmMediator isn't executed. How to make the add child resolver work with containers like Application?

Thanks,
Mikhail