Kommentare zu: Flexible Module Loader – a handy tool to review modules in Adobe Flex 3 (Air)

Von: Mihai

Mihai — Fri, 22 Jan 2010 16:09:26 +0000

Hi again,

Sorry, I tried again and it load my modules, after restart the application.

Mihai

Von: Mihai

Mihai — Fri, 22 Jan 2010 16:03:05 +0000

Hi
I tried this application. Tried to load some swf modules that load some fonts and display they intro a label repeater.
This applications doesn’t load my modules.

Mihai

Von: Simon Biemer

Simon Biemer — Mon, 19 Oct 2009 08:22:36 +0000

Hi Raymond, you have to import the component of your module. For example your module component is ‘TestModule.mxml’. In your example, the code must look like this:

var module:TestModule = factory.create() as TestModule;

(FlexBuilder will automatically import your TestModule component, including ‘import components.TestModule;’ in your parent application)

Now, you can call every property or function of the module like ‘moduls.testFunction()’ or ‘module.width = 100;’…

Greetings, Simon

Von: Raymond

Raymond — Thu, 15 Oct 2009 00:09:05 +0000

Hi Simon,

Thanks for the quick response. I believe you are referring to the following line of code :

var factory:IFlexModuleFactory = IFlexModuleFactory(e.target);
var module:Module = factory.create() as Module;

How did you import your module component in the parent application ? I don’t think you are referring to import mx.modules.Module;

Von: Simon Biemer

Simon Biemer — Wed, 14 Oct 2009 15:20:30 +0000

Hi Raymond, it wasn't implemented yet, but i tried it out and it works fine. I chose a very simple way. I don't know if it is flexible enough for your problem, but at least it is one way how it works. In your handler, which is called after the 'ready' event, you create your module with the interface IFlexModuleFactory, something like factory.create(). At this point, you have to cast the created Object to your Module.mxml. For example your module is TestModule.mxml than call factory.create() as TestModule and write it at a variable of your choice. Now you can call every property or function of the module. However there is still one problem. You have to make an import of your module component in the parent application. If this is no problem in your scenario, than we have fixed your problem. Hope I could have helped you again. Greeting Simon

Von: Raymond

Raymond — Tue, 13 Oct 2009 04:58:25 +0000

Hi, Simon,

I wonder if you have tried successfully to send parameters from the parent to the child module using the following technique published by ESOFTHEAD ?

i am at my ends trying to get the parameters across to the child module. In order to recognise the child module, i don’t seem to have a choice but to use the tag.

How would you use moduleLoader with the ESOFTHEAD’s sample ?

Von: Raymond

Raymond — Thu, 16 Jul 2009 04:53:36 +0000

Hi Simon,

Thanks for the validation. Mine was a unique problem where I had more than one mxml. Its quite a big application, so i have used the mxml components to load the module.

I found that in this respect, the parentApplication does not apply to the component mxml that loads the module but to the “main application (mxml)”. Once i have inserted in the functions and variables in the main application, the parentApplication works.

Thanks for your time.

Greetings,
Raymond

Von: Simon Biemer

Simon Biemer — Wed, 15 Jul 2009 13:52:33 +0000

Hello Raymond,
glad to here about your successful implementation. I created a small test scenario with the FlexibleModuleLoader. When my module call parentApplication.function(param) everything is working fine. The paramter is transmitted correctly into the parent application. Don’t forget to set your function to ‘public’ in your parent application and be sure that your function is really in the mx:Application component and not in some underlying actionscript classes or mxml components. Feel free to post a code snippet here, so I will get some more details…

Greetings, Simon

If I set my function in the parent application to ‘private’, i got the same error as you. So I think you problem could be solved if you change your visibilty modifier (‘private’ to ‘public’) of your function in the parent application. Please let me know if the problem is solved.

Von: Raymond

Raymond — Wed, 15 Jul 2009 03:17:49 +0000

Hi Simon,

I myself have modified ESOFTHEAD’S BLOG posting and have used the Loader.loadBytes() method to load modules from anywhere in the file system successfully.

I am having problems passing parameters to and from the main application to the module. A function call using parentApplication.function() in the module(SWF) gives me a ReferenceError:Error #1069 : Property not found.

Have you encountered this problem before ?

Von: Simon Biemer

Simon Biemer — Fri, 10 Jul 2009 13:45:34 +0000

Hi Prabodh, hope I am capable to help you. Therefore I need a more detailed explanation. How do you embed your font? In mxml with mx:Style or in actionscript with [Embed(source='..', fontName='...', mimeType='..')] ? Be sure, that your root tag is mx:Module. If it is possible post your code of your module and i try to reproduce the error. Greetings, Simon