Ok ... so my replace plugin hack worked. Now I got the next little issue:
- If a module declares a type which was declared somewhere else, I am getting errors in the browser, however the application still seems to work. Is there a way to tell the system to not fire errors if a type was already declared? Chris Am 23.08.20, 22:04 schrieb "Christofer Dutz" <[email protected]>: Ok ... so I got even further. If I modify the TestAModule__deps.js file and replaced the "../../../" prefixes with "../../../main/TestAModule/". It seems to work ... so is there a way to have this generated by the compiler? Otherwise I'll probably just have to use a replace maven plugin to modify the files. Chris Am 23.08.20, 21:24 schrieb "Christofer Dutz" <[email protected]>: Ok ... so it seems to be picking up the "TestAModule__deps.js" correctly ... However this tells the application to load stuff from the root (No idea why all entries there have "../../../" as prefix. But it seems all output files of Royale have this 3-segment prefix. Chris Am 23.08.20, 20:57 schrieb "Christofer Dutz" <[email protected]>: Hi all, today I extended my experiments to loading of modules. So as soon as a user logs in, it gets a list of modules he’s allowed to use. Then the application dynamically loads only these modules. So I managed to get the ModuleLoader to correctly load the css file from a subdirectory: <j:SectionContent name="TestAModule"> <j:ModuleLoader height="100%" width="100%" autoLoad="true" moduleName="TestAModule" modulePath="main/TestAModule"/> </j:SectionContent> In the browser I can see it loading some stuff from the subdirectory “main/TestAModule” … unfortunately it tries to load the js file “TestAModule.js” from the root and not from that sub-directory. What do I have to do to make it load this from the right place? Chris
