Comments on: Mate examples: #8 Modules Example (pt 1) http://www.flexstuff.co.uk/2009/08/18/mate-examples-8-modules-example-pt-1/ Stuff about Flex. And Air. Oh and Flash. And probably about other stuff as well. Who knows? Wed, 25 Jan 2012 18:56:19 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: gillesguillemin http://www.flexstuff.co.uk/2009/08/18/mate-examples-8-modules-example-pt-1/comment-page-1/#comment-126 gillesguillemin Mon, 24 Aug 2009 07:42:42 +0000 http://www.flexstuff.co.uk/?p=552#comment-126 Well, creating the Module is already coupling somehow so I don't really see what's wrong in affecting some properties along the way. Don't also forget that if you want to address a specific subcomponent from the main application you can pass a property like targetSubComponent along with your event for example. Every sub-component will catch it but you can then easily check which specific one is being targeted. Have a look on <a href="http://www.flexstuff.co.uk/2009/08/06/mate-examples-9-modules-example-pt-2/" rel="nofollow">the second example</a> as well, it might give you some other ideas on how to deal with your problem. Well, creating the Module is already coupling somehow so I don’t really see what’s wrong in affecting some properties along the way. Don’t also forget that if you want to address a specific subcomponent from the main application you can pass a property like targetSubComponent along with your event for example. Every sub-component will catch it but you can then easily check which specific one is being targeted.
Have a look on the second example as well, it might give you some other ideas on how to deal with your problem.

]]> By: Gareth http://www.flexstuff.co.uk/2009/08/18/mate-examples-8-modules-example-pt-1/comment-page-1/#comment-122 Gareth Mon, 24 Aug 2009 01:29:24 +0000 http://www.flexstuff.co.uk/?p=552#comment-122 Excellent examples, and I look forward to the next part. Got a couple of questions in regards to Modules, Flex and Cairngorm. When using Modules, what is the best way to manage more than one of the same entity from the main application to the Module. For example, I have a list of users, the user clicks on a user, I want it to load that user in a User module, before closing that User module, I want to load a different user from the main application. Single Main -> Multiple Sub Application properties are o.k, but Multiple Main -> Single / Multiple Sub Application properties???. I can do it by setting the property when I create the Module, but this is coupling? is there a better way to do it? My latest thought is to have a more generic identifier, that can be used so that the module does the hard work of getting information about the identified entity, disconnecting it from the main application in a way, but what if that entity changes in my main application? Cheers Gareth. Excellent examples, and I look forward to the next part. Got a couple of questions in regards to Modules, Flex and Cairngorm.

When using Modules, what is the best way to manage more than one of the same entity from the main application to the Module. For example, I have a list of users, the user clicks on a user, I want it to load that user in a User module, before closing that User module, I want to load a different user from the main application. Single Main -> Multiple Sub Application properties are o.k, but Multiple Main -> Single / Multiple Sub Application properties???. I can do it by setting the property when I create the Module, but this is coupling? is there a better way to do it?

My latest thought is to have a more generic identifier, that can be used so that the module does the hard work of getting information about the identified entity, disconnecting it from the main application in a way, but what if that entity changes in my main application?

Cheers
Gareth.

]]>