Greetings,
I am currently in the planning/design stages for a plugin architecture I will need for my next project. I have never constructed a plugin architecture before but my research has pointed me to the use of Flex “Modules” to load a plugin at runtime. I originally started researching that after reading the first response here: http://www.kirupa.com/forum/showthread.php?351345-plugin-architecture
When I read about creating modules the documentation seems to suggest that every class I have should extend the Module class, and therefore every class that I have should be an independent module. But this isn’t really what I want. I want to be able to load 1 class, 5 classes, or 100 classes into my system depending on what the plugin is adding.
Is there a common practice for creating one Module subclass definition while using that definition to load in a group of classes?
To add some context, these plugins will just be providing concrete class definitions for interfaces and/or abstract types which are understood by my main application - so I’m not loading these plugins to somehow “run” them, I’m just loading them to gain access to their concrete classes which I will instantiate in my main application at a later time.
Help with that question and any other direction about designing an Actionscript plugin architecture would be appreciated.
Thanks.
Matt
