Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought


Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Show Posts

| * |

  Show Posts
Pages: [1]
1  Announcements and General Discussion / Architecture / True Modularity on: July 17, 2008, 11:01:28
I am a little confused with the modularity concept. I have an app that has a main swf (major view components) and the module swfs, which contain the specific view components for the pieces of the app loaded at runtime (based on settings).

The problem I see, which the Modularity demo has as well, is that all the module (CoolWidget) code is compiled into the main swf and the module swf. The ApplicationFacade references the StartupCommand, which references the CoolWidgetMediator and CoolWidget mxml views. My module swfs have a lot of view code, so in a true modular app, it seems wasteful to have all that code compiled in the main swf too...however, I cannot instantiate the Module mediator class without having that class compiled in the main app swf, and if I do that, all the view code comes with it. Thoughts???

Thanks,
Kevin
Pages: [1]