Build failed in Jenkins: royale-asjs_MXTests #287

See Changes: [noreply] text property in Spark TextInput -- [...truncated 726.97 KB...] [royaleunit] Stopping server ... [royaleunit] End of

Re: [royale-compiler] branch develop updated: royale-maven-plugin: BaseMojo provides missing mxml-2009-manifest.xml that is required to use core types like Array, String, Boolean, etc. in MXML (closes

Is there a reason this wasn't fixed by changing the *.xml files in royale-maven-plugin/src/main/resources/config? I would rather not see this in code. Of course, I could be wrong... -Alex On 12/9/19, 1:29 PM, "joshtynj...@apache.org" wrote: This is an automated email from the ASF dual-ho

Re: this in closures

Hmmm... odd. However, I'm not sure that it's actually treated differently from other warnings. If I create a variable without a type, like this: var zzz; I also see the warning at the end, after the success message, like this: The project 'RoyaleClosureThisWarning' has been successfully compile

Re: Jewel Tooltip and TooltipLabel

The Basic Label already has an 'html' as well as a 'text' property. I don’t know if there is a way to only have one property instead of two. I think there are cases where you have to know that the string is meant to be interpreted as HTML or not. Otherwise, I'd love to collapse the two into on

Jenkins build is back to normal : royale-asjs #338

See

Re: Object.defineProperty in prototype

btw I am still happy to look into the possibility of doing a first time 'get' access for the Class itself on its package that runs static code, but as Alex pointed out, it could have issues with the minified version, so it is more at 'investigate' rather than 'solution' stage. I have not prioritize

Re: Object.defineProperty in prototype

This might be a good candidate for getting the static initialization code block working (it is currently not in js). We discussed that recently in another thread. public class MyClass{ {//static init block COMPILE::JS{ Object.defineProperty(MyClass.prototype,"0", { "get

Re: Object.defineProperty in prototype

Identifiers cannot start with a number, so that probably won't work. -- Josh Tynjala Bowler Hat LLC On Mon, Dec 9, 2019 at 9:00 AM Alex Harui wrote: > Did you try: > > function get 0():XML { return this; } > function set 0(value:XML) {} > > Within a COMPILE::JS, I think

Re: Object.defineProperty in prototype

Did you try: function get 0():XML { return this; } function set 0(value:XML) {} Within a COMPILE::JS, I think the variables: this["constructor"] this["__proto__"] are available. HTH, -Alex On 12/9/19, 8:27 AM, "Harbs" wrote: In my question to minimize memory requirements in XML,

Re: Jewel Tooltip and TooltipLabel

This is Jewel, so not tight PAYGO. If so, I am for exposing the additional property within tooltip. On Mon, Dec 9, 2019 at 12:15 PM Piotr Zarzycki wrote: > Hi, > > I have found that Tooltip is not able to display HTML - it's only > displaying simple text. > > I see that Toolitip is using Label t

Object.defineProperty in prototype

In my question to minimize memory requirements in XML, I’d like to optimize the zero index accessor. Right now, we have Object.defineProperty in the XML constructor. The byproduct of that is we have a function defined on every single instance of XML. Ideally that should be on the prototype obje

Jewel Tooltip and TooltipLabel

Hi, I have found that Tooltip is not able to display HTML - it's only displaying simple text. I see that Toolitip is using Label to display text internally. I see two solutions to that problem: 1) I'm exposing apart of property tooltip another property called tooltipHtml 2) I'm creating ToolTip

Build failed in Jenkins: royale-asjs #337

See Changes: -- [...truncated 1.17 MB...] [java] var events = require('events'); [java] ^^^ [java] [java] Dec 09, 2019 1:50

Re: this in closures

Why does this warning show up at the very end of the console output (different than all other errors and warnings)? > On Dec 4, 2019, at 1:29 AM, Josh Tynjala wrote: > > It's not possible at this time. > > Java has an annotation for suppressing warnings locally: > > @SuppressWarnings({"unchec