I have finally(!) gotten around to releasing Fabricaton 0.6. This release adds a couple of important new features, Interceptors and Reactions.
Interceptors allow means to alter the normal flow of PureMVC notifications. You can drop notification, change their payload, or send completely different notification in its place, all before they reach the rest of the PureMVC actors, Mediators and Commands. See the wiki page for Interceptors for more details.
Reactions bring a respondTo like convention to mediators for handling component events automatically. A reactToMyComponentFooEvent indicates interest in the FooEvent of the MyComponent and its handler function at the same time. See the wiki page for Reactions for more details.
ChangeLog of what has changed in this release.
Download Fabrication 0.6.
Happy New Year Everyone!
January 13th, 2009 7:08 pm
Impresive stuff, many thanks for sharing. Interceptors is really a good one.
Cheers,
D
January 22nd, 2009 2:04 pm
Hey Darshan, as always, great work. I have a small request. Would it be possible to add a public setter to class ApplicationFabricator for applicationInstanceName. I have a situation where a module is given an ID in an XML file and I need that name to be the instance name, but currently instance names are always ClassName + incremental number. My request is to be able to override this default behavior if I choose by being able to set applicationInstanceName myself. I realize by doing this it becomes my responsibility to ensure the names are unique, which is fine. I’d just like to have the option to use either dynamic generated instance names or explicit ones.
The following change allows both situations, and it’s a small addition. If I don;’t give and explicit one, then the current instance name generation continues as normal.
[code]
public function set applicationInstanceName(value:String) {
_applicationInstanceName = value;
}
[/code]
I’ve already added it to my own Fabrication install, but it would be great to have this in the code base too.
January 24th, 2009 2:28 am
Hey Jason,
This sounds like a good idea and is probably very useful while debugging. I will add this to the svn. And like you mentioned you would have to ensure uniqueness on your own. The instance name must be unique as it is part of the multiton key.
peace,
darshan
February 5th, 2009 2:10 pm
If it helps, I have setup a small example project and wrote an article explaining how to setup an environment to use Fabrication and how reactTo and respondTo works. Feel free to check it out.
http://codeofdoom.com/wordpress/2009/01/27/fabrication-puremvc-cleaned-up/
February 7th, 2009 11:29 am
Thanks Marcel for taking the time to explore Fabrication in such detail. And I loved the “tears to my eyes” comment, made my day!