Hi Darshan
I have had the pleasure of introducing my fabricator gem to two teams at where I work and thus also introducing the Fabrication framework. The primary goal of this is to get feedback to be able to improve the fabricator gem but also improve team development speed.
It seems that we have run into some issues / bugs with the framework and hope that You can help:
1. Release 0.6 of fabrication do not include AirApplication, as workaround we got the source code from subversion and this helped us create an Fabrication AirApplication.
2. ReactTo do not seam to work when you have a non referred component which uses ReactTo. Example we have a module1 that requests an ui component from module2. Module1 has no explicit reference to the ui component from module2, it just add it using Addchild. When module1 requests the component from module2, module2 creates the component and it's mediator, and sends the component to module1. Only addEventListener seems to work in the component for this scenario, reactTo methods leads to Nullpointer exception.
3. onRegister never executes when using Reflexive mediators with mx states. We have downloaded your demo Using Reflexive mediators with Application states and extracted the states-code to a component referenced in the application mxml file. Thus we use <mx:states instead of <fab:states in the component but this results in broken functionality(states), since the code never calls the onRegister method on the mediator of the deferred sub-component. We use this code to register the mediator (new ConfirmMediator(resolve(testView)..confirm).
Last I would love to know what the intentions are with Fabrication. Is it going to be further improved/developed on or is left for others to pick up? The reason I ask is, that we would really like to use Fabrication in production.
Thanx in advance
Steffen