Dynamic Mediators and Notifications

[Dal]

Kia Ora,
Firstly I'd like to say well done to Keith its a nice scaleble framework.

This is my first attempt at MVC and Flash AS3 Framework, I am creating menu structures and stage layouts dynamically dependent on the page that is read in, all my Mediators and Components are created dynamically from recursive simple and macro commands.

What I am finding though is that because I am creating them all dynamically, when sending a notification to the menu for example I am having to have all my mediators receive the notification and react only if their mediator name is the same as that which is sent in the notification......

Although this works, the result is complicated code that is not very easy to follow, I also think that its a little too dependent on each other and not as loosely coupled as it could be - i'm sure if a came back in a month I'd have trouble following it!

Does anyone have an example where they have used dynamic mediators in a different way??


Cheers
~D

[Dal]

sorry clif not  keith I is tired

[puremvc]

You can use the type property as the discriminator, but you're still having to check it. You could create a one or more dynamic notification names that's the sender will use to target a specific receiver without knowing who it is. That would entail dynamically generating one or more strings in the array that the mediator returns when listNotificationInterests is called.

-=Cliff>

[Dal]

Hi Cliff,
Thanks for the thats a ninja move - I know you are probable kept pretty busy.

My listNotificationsInterests is starting to get around 5 or 6 in the array - I know in your documentation you said if it gets over 3 or 4 then you should be looking at segregating them out, is it possible for one component to have multiple Mediators? Is that a wise move?

I would be pretty keen to get your input on the coding at specific points within this project if thats  alright??

Cheers
~D

[Joel Hooks]

A single component can have multiple mediators in the respect that a component is probably made up of sub-components. So say you have a LoginForm, you could technically mediate the submit/cancel buttons and each text input - not that you'd want to, but they are individual components and controls, so they can be mediated as necessary. This applies to your custom components and the sub-components/controls contained within.

It is also technically possible to mediate a component with two separate mediators, but I doubt that cliff would recommend this ambiguous practice.

[Dal]

Hi Joel,
Chur for the reply, what would you recommend then?

I could easily have 10 - 20 functions in my notifcationsList - but it seems like alot and becomes a large switch case statement.....
How would I go about simplifying the coding and not creating a huge document for other users as well as my self??

Cheers
~D

[puremvc]

If you're at the point of having one mediator handling 20 or more events or notifications, then the view component it is mediating is probably too monolithic and should be broken into multiple components, each with its own mediator.

-=Cliff>

[Dal]

chur Cliff
chur Joel

will break it down and go from there.


Cheers
~D