I am not sure I fully understand an idea with a small swf shell firing Flex
modules. My main application page is an html page. So, I could load shell's
swf as such:
swfobject.embedSWF("shell.swf", "mainDiv", "100%", "100%", "14.0.0",
"expressInstall.swf"). The shell swf can expose whatever public methods are
needed to run modules. My question is how and what am I going to pass
around to load a specific module being selected from the main html menu?
Another thing is the the shell must be hidden.
On Mon, Oct 19, 2015 at 12:26 AM Alex Harui <aha...@adobe.com> wrote:
>
>
> On 10/18/15, 8:40 AM, "mark goldin" <markzolo...@gmail.com> wrote:
>
> >My setup is the following:
> >I have an html navigation bar across the screen. I am loading my Flex
> >application by selecting a menu on the bar. That will navigate to an html
> >wrapper that looks like this:
> ><html>
> ><body style="margin: 0px; overflow: auto;">
> ><div id="mainDiv" style="height: 100%; width: 100%; overflow: visible;">
> ></div>
> ><script type="text/javascript" src="swfobject.js"></script>
> > <script type="text/javascript">
> > swfobject.embedSWF("alarms.swf", "mainDiv", "100%", "100%",
> >"14.0.0", "expressInstall.swf", 'someparameters');
> ></script>
> ></body>
> ></html>
> >
> >So, what exactly can I improve?
>
> Hard to say. I think when you started on this path some of us wondered
> why you couldn’t use a shell SWF. Basically, by converting from Modules
> to Applications you have effectively converted from DLL’s to EXE’s if you
> are familiar with Windows. A Module/DLL is smaller and faster because it
> doesn’t have to create an entire process in the runtime. Of course,
> processes give you isolation better than Modules/DLLs, but you pay for the
> construction of that isolation.
>
> Using a shell SWF to load the other sub-application SWFs might help, but
> going back to loading module SWFs will still probably be more performant.
>
> -Alex
>
>
