Perhaps the best solution is to register all mediators and children in the StageMediator constructor and set them all to invisible, then manage their visibility as and when they are needed?

Hello I have a couple of questions...

1) Should all proxies be instantiated and registered together when the application starts? Or can this be done as and when they are needed?

2) I work in a pure AS method, i do not use flex and i am trying to decide the best way to handle the creation and addition of new children to the stage etc...

if my AssetProxy executes:
facade.registerMediator(new ProgressBarMediator(new MovieClip()));

How should i handle the addition to the stage? Is it a bad idea for the Mediator to gain a reference to the stage? Should i send the child as the body of a notification? Should i create the movieclip and attach it to the stage from the command and THEN create the mediator with a reference to the new child?

I cannot seem to find an elegant solution to the management of children.

Many thanks in advance.

Sounds great!

OK great,

The only thing i cant decide is startup flow... does the following sound correct?

StartupCommand - sends LoadAssets notification
LoadAssetsCommand - tells AssetsDataProxy to loadAssets()
LoadAssetsCommand - creates ProgressBarMediator and views etc
ProgressBarMediator - listens for AssetsLoading Notifications from the AssetsDataProxy
AssetsDataProxy  - sends AssetsLoaded Notification
AssetsLoadedCommand - removes ProgressBarMediator & views etc then continues with app

Is this a bad approach?

Thanks.

I have a separate swf that contains all graphic assets for my app.

I cannot decide where the logic for preloading should go...

Somewhere it has to interact with a view to display the load progress.

Should the loading logic be placed into a proxy and dispatch a progress notification  ?

If so how would you use the "data" property of the proxy? to hold the "LoaderContentInfo" of the loaded swf and then provide a getAsset() method?

any thoughts?

Thanks.

Could you explain further?

The calls are split across proxies...

Hi,

I am having trouble making a design decision...

When a user clicks on a category from the menu the following needs to occur:

1) The MenuMediator sends a notification which is bound to a LoadCategoryCommand

2) The LoadCategoryCommand needs to check which view and mediator to load

2 a) LoadCategoryCommand asks the CategoryProxy if the selected category owns any child categories. If so load the category view. If not -> 2b
2 b) LoadCategoryCommand asks the ProductsProxy if the selected category
owns any products. If so load the product view. if not -> 2c
2 c) LoadCategoryCommand asks the PageProxy is the selected category owns a page. If so load the page view. If not redirect the user / display error.

My problem is that the LoadCategoryCommand cannot listen for updates from the proxies, and the proxies must dispatch an event because they are loading XML from a remote URL...

Where should I handle the updates from the Proxies, and then decide which view to load.

Yeah i cant seem to pin-point what is causing this problem, it is definitely something to do with events.. somewhere.

I will investigate further when i have time.

OK... it turns out this is some sort of AS3 Bug.

Imagine the following hireachy: Stage->MenuMC->ItemMC->ButtonMC

The actionscript from the first frame of ButtonMC is being ignored. This seems to be for all children at or above level 2 (Stage being level 0)

I cannot seem to figure out what triggers this bug but it does not happen when i add the menu items BEFORE instantiating my URLLoader.

For the moment i have moved all code to frame2 which isn't a very elgant solution. Is anyone else familiar with this problem?

Erm.. movieclips in flex have timelines.
And you have a thick kludgy pointless framework to trip you up

Joel i do'nt think you have understood the problem

MenuMC is a movieclip of the menu.

MenuItemMC is an individual menu "button" & text etc.

The anonymous function works fine and the notification is dispatched.

The problem is that when i add children to the stage after receiving a notification they ignore their time line scripts

The actionscript is ignored, e.g the stop() command on the first frame of MenuItemMC

Sorry i forgot to mention i have the same problem on the event listeners on the menu buttons as i do on the event listeners on the url loader.

yes, the following happens..

MenuMediator Loads and asks CategoriesProxy to loadCategories()

loadCategories invokes my httpservice and parses the XML

When MenuMediator hears ApplicationFacade.MENU_CATEGORIES_LOADED it calls buildMenuItems()

these items, when added to the display list, are broken.

If i call buildMenuItems() directly from the constructor, and comment out loadCategories() they appear as they should do.

Erm... of course it does. Try for yourself.