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: Multiple UI's per mediator - no specific viewCompoment on: March 11, 2010, 04:03:43
Cool, cheers.
2  Announcements and General Discussion / Getting Started / Multiple UI's per mediator - no specific viewCompoment on: March 09, 2010, 04:43:18
Hi,

I'm trying to build a little Guitar Hero-esque game to try to get my head around PureMVC. I've got three targets on my screen corresponding to three buttons, when  a button is pressed the visual state of the target changes and returns to normal when the key is lifted.

The various state information for the target is held within the target class and I have a TargetMediator class switching the sate of the relevant target when necessary. The TargetMediator class is created and the three targets are created within the TargetMediators onRegister function.

It seems to be working ok, but I'm not registering a view component for the TargetMediator and am wondering if all mediators need to have a registered viewComponent or if they're ok to function like this, handling a few diffeent objects without being bound to one specifically. It seems bad practice to be not to have a registered view component, but it would seem superfluous to have three TargetMediators, one for each target, when they're all doing the same thing anyway.

Any advice/sugestions? Is what I'm doing ok or have I missed the mark?

Cheers,
Ed
Pages: [1]