royale-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: How to Set Path in UIModuleLoader
Date Tue, 03 Apr 2018 06:32:12 GMT
Hi Doug,

I was just trying to understand what the Flex code looked like to make
sure you were using the right Royale code.  IIRC, in Flex there was a
ModuleLoader that loaded a Module and created a single instance of its
main class, expecting it to be UI.  I didn't think you could pass
parameters to it when loading.  There was also a ModuleManager that loaded
modules that extended ModuleBase.  That one I think you could pass
parameters.  I don't think we've created a Royale equivalent for
ModuleManager/ModuleBase scenarios.

Note also that Royale modules do not unload at this time.  Probably for a

Have you run the examples/royale/ModuleExample?  It sets up the
bin/js-debug output in a particular folder structure and I think a bit
differently for bin/js-release.  Maybe that example will contain the clue
you need.


On 4/2/18, 10:58 PM, "doug777" <> wrote:

>Hi Alex,
>Main.mxml contains initialView/View and a bunch of getters and setters.
>Inside this View is a header group, a body group that contains the modules
>and a footer group. Originally the modules were contained in a ViewStack,
>but I've written something I hope will replace this, but I can't check it
>until the modules can build.
>The first module gets data from CF and then depending on the choices the
>user makes, the second module gets appropriate data from CF and is
>in place of module 1 and so on depending on the choices made in each
>The modules can appear in any order depending on user choice.
>I'm not sure what that has to do with getting the modules in the build,
>basically that's how it works.
>Sent from: 

View raw message