RE: Issue when extending mx.Core.Application

[Yishay Weiss]

Hi Nicolas,

I’m not sure if we’re on the right thread here but I can’t understand what this 
asconfig.json is doing, and why MXRoyaleJS.swc is added separately in the 
library path.

For what it’s worth, here’s the asconfig.json I used for my emulation examples.

{
  "config": "flex",
  "compilerOptions": {
      "debug": false,
      "targets": ["JSRoyale"],
      "source-map": false,
      "source-path": ["src"],
      "html-template": "index-template.html",
      "js-compiler-option": [
          "--skip_type_inference"
      ],
      "js-external-library-path": ["libs"],
  },
  "copySourcePathAssets": true,
  "files":
  [
      "src/Examples.mxml"
  ]
}

From: tranquiliste<mailto:nicolas.agut...@gmail.com>
Sent: Thursday, July 23, 2020 9:56 AM
To: users@royale.apache.org<mailto:users@royale.apache.org>
Subject: Re: Issue when extending mx.Core.Application

Hello Carlos,

Thanks for your answer.

I don't knwow which part o f the configuration may be faulty
I am using Visual Studio Code as IDE and the BowlerHatLLC extension
My compiler options is as followed
{
    "compilerOptions": {
      "targets": ["JSRoyale"],
      "source-path": ["src"],
      "source-map": true,
      "library-path": [
        "${royalelib}/js/libs/MXRoyaleJS.swc"
      ],
      "js-library-path": [
        "${royalelib}/js/libs/MXRoyaleJS.swc"
    ],
      "html-output-filename": "TestApp.html"
    },
    "mainClass": "Test"
}



-----
Nicolas
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/