Hi,

In Pure ( as in Fabrication ) models should not be shared between shell and modules. Separate facades provides "the wall" wich should be crossed only by using notifications and passing objects with them.

Don't know why, but it seems to work this way http://www.flexthinker.com/2010/03/flex4-moduleloader-and-runtime-skins/. You have to remember to add ModuleLoader ( FlexModuleLoader ) to display list BEFORE you start loading module.

This is bad situation because in this case new FabricationModuleLoader and FabricationAirModuleLoader classes ( based on ModuleManager ) won't work properly.

Welcome,

Finally, I managed to port my old Tequila app and now I can present you FabricationConsole application.
Updates in 0.7.4 version:

• added logging functionality
• added support for FabricationConsole (v. 0.1)
• compiled with Flex SDK 4.1.0.16076

Ok, is there any chance you to provide me with a little example of the issue?

Hi,

Fabrication is compiled against Flex 4.0 so I don't know if this could be an issue, but I doubt it. Please, try 0.7.3.1. It has very important bug fix related to components and application domains. I'm not 100% sure, but this could be a reason why loaded module can't access style definitions from shell.

Hi,

Which version of fabrication and Flex SDK you are using?

Hi,

try update ( 0.7.3.1 ) on project page. I've tested it on the same example you did and no errors at this point. Hope will work for you!

Hi spacetimer,

Thanks for this post, you've pointed out very important issue. The problems is in new reflection mechanism ( which not exists in 0.6 ). REflection mechanism can't find loaded module-related classes because they are held in separate domain. I will fix it and let you know. Thanks again!

Ok, my mistake, wrong library uploaded to google, try again.

Hi,

Version 0.7.3 adds support for flex3 ( moxie ) version as requested from manu users. You can check full
changelog here.

Please, try new 0.7.3 version with moxie builds.

Yes, you're right. There is one spark dependency in ComponentResolver class - it had to be added to make
deferred mediator registration in flex4. I will try to make it work without referring to spark package, will let you know about this.

Hi,

Please, try new FabricationAirModuleLoader class wich supports module loading for AIR apps. Here you can find some descriptions and examples.

ChangeLog: http://code.google.com/p/fabrication/wiki/ChangeLog

Updated wiki and added new examples:

• IoC mechanism
• New reactions
• Notifications via namespaces
• FabricationModuleLoader and FabricationAirModuleLoader examples

I will provide some examples in short time. Actually, benefit of using these loaders over standard FlexModuleLoader is that we do not create another layer of fabricator ( FlexModule loader is IFabricator ) but we are just using pure FlexModule ( loaded FlexModule is fabricator by itself )