Before you go down the path of working with modules, I’d recommend making sure you actually need them.
I think you’ll find it’s very rare to have a case where modules will help. I have applications with 1200 classes and hundreds of thousands of lines of code. It compiles down very small and loads lightning fast. What are you trying to solve with modules? > On Mar 25, 2025, at 5:54 PM, Jim McNamara <[email protected]> wrote: > > > Hi, > i am very excited to learn about modules. > I get some of it but need help with this one topic. > > https://github.com/apache/royale-asjs/tree/develop/examples/blog/BE0013_Dividing_an_Apache_Royale_application_with_modules > > In the 2 config files one for main and one for module what are the config > file names for e.g. > > Question 2 - what is the purpose of gccvars.txt and gccprops.txt and > modgccvars and modgccprops > > I saw the layout here and I get that but I need to get the piece below... > thanks for any additional help you can render this support comes from the > following page... > > https://apache.github.io/royale-docs/features/modules > > I am definitely interested in modules because i will have several screens on > my upcoming app at least i hope i will. thanks j. > > <royale-config> > <js-compiler-option> > <option>--variable_map_output_file gccvars.txt</option> > <option>--property_map_output_file gccprops.txt</option> > </js-compiler-option> > </royale-config> > > Here’s the config for the module: > > <royale-config> > <js-compiler-option> > <option>--variable_map_input_file > ../../../MainApp/bin/js-release/gccvars.txt</option> > <option>--property_map_input_file > ../../../MainApp/bin/js-release/gccprops.txt</option> > <option>--variable_map_output_file modgccvars.txt</option> > <option>--property_map_output_file modgccprops.txt</option> > </js-compiler-option> > </royale-config> > > > > > Sent with Proton Mail secure email.
