No problem, it's a great demo.

Keep an eye out for the silverlight port coming VERY soon

Cool,

Just one more final thing =)

Wouldn't it be better off being:

:

sendNotification(ApplicationFacade.APP_STATE, ApplicationProxy.VIEWING_LOGIN_SCREEN);


One final thing, where does the new command get triggered to set the initial state?

This demo isn't in the repo is it? The only one i can find is the book store.

This was from the zip file, i'll have a look in the repository too.

Matt

Hi Sectore,

I am currently in the process of porting this demo over to silverlight, along with the C# PureMVC port i'm working on. But i'm having a problem which i'm not sure weather it is the demo, or my port.

My question is this.

From what i can tell, the ApplicationMediator is registered with the Facade via the ViewPrepCommand which is triggered by the application startup code telling the facade to notify observers of an APP_STARTUP notification.

In the ApplicationMediators listNotificationInterests method, it says that it is interested in the APP_STARTUP, which i beleive it uses to setup its sub views.

Now the thing that i am having dificuilty with is that the ApplicationMediator is registered by the APP_STARTUP command, and is interested in the APP_STARTUP but my ApplicationMediator doesn't currently receive notification (i'm guessing because it's not in the list when the APP_STATUP notification was broadcast)

So should the ApplicationMediator be subscribing to the APP_STARTUP notification? or is there something wrong with my port that i can't add mediators during the handling of a notification which should then receive the notification themselves?

I hope this makes sence.

Many thanks

Matt

If this is now the recomended way of starting up an application, could we add a startup method to the IFacade interface? I prefer to hold the facade in an IFacade typed variable as apposed to a MyApplicationFacade typed variable.

What do you think?

Matt

ok, i'm happy to go with this (could help with things like mono and backwards compatability)

We will definatley be using NUnit for the unit tests.

Going through the AS3 implementation, Cliff has made a concious decision no to use some datatypes so as not to tie down the implementation.

When it comes to silverlight and .NET though, the core datatypes are not as flexible as their AS3 counterparts (ie Arrays require a size and can't be indexed by name)

So to what degree should we implement the .NET datatype? We could use relitivley low level ones such as ArrayList and Hastable? or go the whole hog and use Generic collections which gives type safety?

Any thoughts?

Matt

Well i've made a start on porting this over to Silverlight / C# and have narrowed down the problems.

One of these issues is the implementation of the Observer pattern.

Could / should this be done using delegates? or should we have use the Observer class and use reflection (which delegates seems to do anyway) to keep it generic?

What do you think?

Matt