Build failed in Jenkins: royale-typedefs #845

See -- Started by timer Building on master in workspace > git.exe rev-parse --

Build failed in Jenkins: royale-asjs_jsonly #1843

See -- [...truncated 431.45 KB...] [java] [java] 4903 bytes written to C:\Program Files (x86)\Jenkins\workspace\royale-compiler\compiler\target\

RE: Getting An Emulation Component To Run

Hi Alex, You have created an Example in royale/ModuleExample Contains two files in different projects : MainApp.mxml and Module.mxml MainApp uses UIModuleLoader and it loads the modules with moduleName & modulePath properties. UIModuleLoader extends UIBase In MXRoyale, ModuleLoader extends VBox

Build failed in Jenkins: royale-compiler #539

See -- [...truncated 137.39 KB...] [java] Loading configuration:

RE: Getting An Emulation Component To Run

Hi Alex, You have created an Example in royale/ModuleExample Contains two files in different projects : MainApp.mxml and Module.mxml MainApp uses UIModuleLoader and it loads the modules with moduleName & modulePath properties. UIModuleLoader extends UIBase In MXRoyale, ModuleLoader extends VBox

Re: Revisiting the old debate: 'localId vs. id'

The underlying JS runtimes are highly tolerant of bad code. We should be too, IMO. I get it. But please let's not make that the marketing slogan :) On Mon, Nov 5, 2018 at 8:39 PM Alex Harui wrote: > IMO, the benefit of choosing "words" instead of "true/false" "on/off" > Booleans is that you c