What's new:

• added fabrication namespace ( http://puremvc.org/utilities/fabrication/2010 )
• AirApplication/FlexApplication for spark and AirHaloApplication?/FlexHaloApplication? for halo architecture
• Introduced FabricationModuleLoader? and FabricationAirModuleLoader - simplified way to manage modules using ModuleManager
• Introduced new Reactions registration approach wiki
• Introduced simply IoC for fabrication actors wiki

I'm working on couple of examples how to use new features. Stay tuned, and waiting for your feedback.

Rafal.

Hi Manuraj,

This could be the same problem as last time. Please, chek if you have property [lcfirst(eventSourceName)] declared as a public getter in your mediator.

Can you send me your code example?

Ok, please tell me - in onRegister in NavBarMediator this getter ( someButton ) returns good value ( reference ) or maybe null?

Added to links on project page.

Sure, it's done.

Hi,

AsyncFabricationCommand is present in latest Fabrication release ( v. 0.7 ).

It is not easy operation to load module into AIR app, not only in fabrication. I will upload an example how to do that in shot time.In meanwhile, try to look at this: http://blog.esofthead.com/loading-modules-in-air-application-2/

Hi,

As I promised, next version of fabrication is ready. With some fixes ( mostly reflexive registration issues ) and full flex4 support. AS always, you can check it on project site.

Hi everyone,

My name is Rafal and from now on I will be responsible for bringing Fabrication back to life!. I'm author of Tequila project ( wich is based on Fabrication ) and. after short discussion with Darshan, we both decided that I will take over his project.

So, what you can expect in nearly feature:
- flex4 compatibility
- further improvements ( simpler reactions, metadata support, namespace notifications etc ).

Please, wach out for any changes and comments on project page. I will try to post any updates here on this forum too.

Best regards,

Rafał Szemraj

Yes, this is done intentionally. You shouldn't access one proxy from another one, it is bad practice. Instead you should always use commands to manage proxies operations.