Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

* | |

  Show Posts
Pages: [1]
1  Announcements and General Discussion / Getting Started / Re: how to use sendNotification inside Model on: June 12, 2008, 09:07:59
Also - you won't need a load method if you don't register the Proxy with the startup monitor.  You only need to register proxies with the startupmonitor that need to load resources at startup.
2  Announcements and General Discussion / Getting Started / Re: Making a Flash Game using PureMVC on: June 12, 2008, 09:00:02
Just curious if the original poster has any follow up on the game.  Did you make it?  What decisions did you make for how the objects of the game fit into the mvc pattern? 


One question that I am struggling with is where a sound player belongs - is that a view component?

Thanks
3  PureMVC Manifold / Demos and Utils / Re: Startup as Ordered - A PureMVC AS3 / Flex Demo on: June 06, 2008, 07:13:16
But - the notifications carry the resource name in the body. 
4  PureMVC Manifold / Demos and Utils / Re: Startup as Ordered - A PureMVC AS3 / Flex Demo on: June 05, 2008, 10:28:07
Question about the tutorial:

In part 2 you have made the statement:

Lines 33-37: The before mentioned utility commands are registered. It’s important that the commands are registered separately with the “Loaded” and “Failed” notification names for every single startup resource.


Why is it important that there are different notification names for every startup resource?


5  PureMVC Manifold / Demos and Utils / Re: Application Skeleton - A PureMVC AS3 / Flex / WebORB Demo on: May 26, 2008, 01:31:40
I agree - in the MainScreen.mxml file you have this

      
:
<mx:Label text="{ApplicationFacade.getLocaleProxy().getText('How to read config values')}" color="#ffffff" fontSize="14" width="90%" />
<mx:Text id="configValueExample" width="90%" color="#ffffff" />
<mx:Label text="{ApplicationFacade.getLocaleProxy().getText('How to read locale text')}" color="#ffffff" fontSize="14" width="90%" />
<mx:Text id="localeValueExample" width="90%" color="#ffffff" />


Which is a mix of having the mediator give the text (for the mx:Text) controls and having the view component talk to the ApplicaitonFacade directly.  Seems it ought to be changed to this


:
<mx:Label id="configLabel" color="#ffffff" fontSize="14" width="90%" />
<mx:Text id="configValueExample" width="90%" color="#ffffff" />
<mx:Label id="localeLabel" color="#ffffff" fontSize="14" width="90%" />
<mx:Text id="localeValueExample" width="90%" color="#ffffff" />

And then in

MainScreenMediator in the handleCreationComplete function add these two lines.
:
this.mainScreen.configLabel.text= ApplicationFacade.getLocaleProxy().getText('How to read config values');
this.mainScreen.localeLabel.text = ApplicationFacade.getLocaleProxy().getText('How to read locale text');


Pages: [1]