Re: Jewel CSS winding up in non-Jewel apps

Is the "isNative()" function hooked up to the native keyword or the [native] metadata? This is not the gotcha I was trying to remember in my last post, but one concern that came to mind was that some API that we consider "native" or a "typedef" for JS in the browser because it is supplied by th

Jenkins build is back to normal : royale-asjs_MXTests #922

See

Build failed in Jenkins: royale-asjs_MXTests #921

See -- [...truncated 944.66 KB...] [mxmlc] scanning for overrides: DeviceNames [mxmlc] scanning for overrides: DispatchKeyEvent [mxmlc] scanning

Re: Jewel CSS winding up in non-Jewel apps

It looks like the native keyword is allowed on functions only. You'll get a compiler error if you try to add the native keyword onto a class. After discovering this, I looked at how classes are compiled into playerglobal.swc, and it looks like they have [native] metadata. That could possibly serve

Re: Tour de Jewel regression in Jewel Alert (release version)

Since this seems all related to the change Josh propose (use of native), I'll focus in other documentation task for now. thanks! Carlos El mié., 10 jul. 2019 a las 0:13, Alex Harui () escribió: > Other typedef SWCs beside js.swc should have .js files in them and the > compiler should be picki

Re: Jewel CSS winding up in non-Jewel apps

Using "native" keyword sounds and good solution and very cool. :) El mié., 10 jul. 2019 a las 5:08, Alex Harui () escribió: > Good idea. I have this vague memory that there are some other gotchas > around using "native", but give it a try and see what happens. > > -Alex > > On 7/9/19, 4:21 PM,

Re: Maven build and URLSearchParams

https://github.com/apache/royale-typedefs/blob/develop/js/src/main/config/externc-config.xml#L89 Which should be created by: https://github.com/apache/royale-typedefs/blob/develop/js/build.xml#L99