Interesting. I skimmed the link provided. The ModuleManager already returns an IModuleInfo that contains a factory so I don’t quite get any need for a DynamicFactory class.
You should be able to create a project and switch it to use <mx:Module implements=”MyModuleInterface” > instead of <mx:Application>. The project will need access to the MyModuleInterface source or swc. As long as teach time has that set up, they can independently develop modules. Then as long as you use ModuleManager to load that module everything should work just fine. The only real question is whether you should optimize out classes or not. It will depend on your desire to re-use these modules in different apps. However, I would encourage you to briefly read the doc on the Marshall Plan as you may want to use sub-apps instead of Modules if you are going to have these things developed on different versions of the SDK some day. On 2/17/10 8:59 AM, "gtb104" <[email protected]> wrote: Thanks for the link Robert. I guess that I'm slightly frustrated because what I want doesn't seem to be unreasonable, and is what I expect modules to provide. I just want 2 teams of developers to be able to create code that can be put together, at runtime, that communicate with a set interface. These two sets of code should have no knowledge of each other. I guess it would be like adding someones SWC to your code path to get the functionality, without actually adding it to your code path so that your SWF bloats. --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "ag_rcuren" <robert.vancuren...@...> wrote: > > This sounds very similar to a project I worked on. Here is post I made a > while back that might help you. > > http://flexinonroids.wordpress.com/2009/05/27/flex-3-dynamically-loading-components-at-runtime/ > > The app I ended up creating knows how to load modules (that are not optimized > to ensure they contain everything they need) that implement an common > interface so the app knows how to use them. When the app runs it pulls of > list of all the available modules from a database and then can load and use > them. > > --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , > "gtb104" <gtb104@> wrote: > > > > Reading the Flex Docs gave me the impression that you can create modules > > that have no direct dependencies to the main app, but I can't figure it out. > > > > Basically, I want a team of developer somewhere else to create a module > > that's coded to an interface. I then want to load that module, potentially > > from their server, and cast it to the interface that's defined on my > > system, and use the interface methods. > > > > I'm not having luck though. Most examples show the main/interface/module > > all physically located in the same package. I need them to be in different > > projects... projects that have NO dependency with each other. > > > > I've tried finding info on the web as well, but no luck. Does anyone know > > of a resource, with code example? > > > > Thank you in advance! > > > > One last question. The module that the other team is creating, does that > > have to be created in a flex project, or can you make it in a flex library? > > > -- Alex Harui Flex SDK Team Adobe System, Inc. http://blogs.adobe.com/aharui
