Build failed in Jenkins: royale-asjs_MXTests #620

See -- [...truncated 2.04 MB...] [mxmlc] using source file:

Issues on GitHub

Hi, I have Created an Issue on GitHub https://github.com/apache/royale-asjs/issues/404 14 days ago But no replies Please reply on that issue Thanks -Pashmina Kazi

Build failed in Jenkins: royale-asjs_MXTests #619

See Changes: [carlosrovira] some users experience problems building with maven and getting rat [carlosrovira] jewel-grid: make grid extend container instead of group and and add

Jenkins build is back to normal : royale-asjs_jsonly #2724

See

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

Using javascript native Reflect is one option. But maybe you can use Object.keys and Object.getOwnPropertyDescriptor to keep compatible with IE11 ? Royale reflection is 'heavier' but gives you more specific support from within the framework. Probably the easiest way to see how to use that is via

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

Hi, > But reflection classes now support it... Just to mention it: Thanks to Piotr we're using Reflection [1] to extract the getters in order create dynamic objects which can be stringified by using JSON.stringify() then. However, would be even better if Yishay's idea or something other on the f

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

Hi Yishay, No I don't think so. I think you can use some filtering options in a replacer function in conjunction with stringify. AMF has something similar for filtering or altering dynamic properties. The longer term solution for this is to have a better implementation for namespaces, and to make

RE: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

Hi Greg, I’m referring to Olaf’s issue [1] with JSON.stringify() using the qualified property names. Could a class alias change the qualification prefix? [1] http://apache-royale-development.20373.n8.nabble.com/Plain-public-variables-complain-they-don-t-have-getters-setters-Was-CreationComp

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

'I’m wondering if registerClassAlias or the RemoteClass meta-tag would solve this. Anyone know?' The issue with public car renaming? I can't see how it could. But reflection classes now support it (you can get and set public var values in release mode via reflection) and AMF works with public var

RE: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

I’m wondering if registerClassAlias or the RemoteClass meta-tag would solve this. Anyone know? From: Harbs Sent: Thursday, March 28, 2019 3:03:46 PM To: dev@royale.apache.org Subject: Re: Plain public variables complain they don't have getters / setters (Was "

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

FWIW, I use a method to convert classes to JSON which allows me to define exactly which properties get written and using what names. i.e. myFoo.toData() > On Mar 28, 2019, at 1:26 PM, Olaf Krueger wrote: > > I would just like to mention that resolving this "public vars" issue by > replacing th

Jenkins build is back to normal : royale-typedefs #1200

See

Jenkins build is back to normal : royale-compiler #790

See

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

I would just like to mention that resolving this "public vars" issue by replacing the public by private vars with getters/setters has a side effect: JSON.stringify() stringifies all getters with the entire package name which makes the JSON representation unusable [1]. [1] package com.mydomain.myap

RE: [Non-DoD Source] Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

smime.p7m Description: S/MIME encrypted message

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

>More specifically, you shouldn’t use public variables as references *within* the MXML. The reason for that is that the references in the MXML are saved as text which might not match the renamed variables when the code is minified. I probably misunderstand something but isn't anything in AS3 a re

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

More specifically, you shouldn’t use public variables as references *within* the MXML. The reason for that is that the references in the MXML are saved as text which might not match the renamed variables when the code is minified. > On Mar 28, 2019, at 11:45 AM, yishayw wrote: > >> Does this h

Build failed in Jenkins: royale-asjs_MXTests #618

See Changes: [carlosrovira] jewel-datechooser; doc, cleaning and organization [carlosrovira] jewel-datechooser: navigation with view selector goes from days to years [carlosrovira

Re: Plain public variables complain they don't have getters / setters (Was "CreationComplete event question")

>Does this have any disadvantages or leads to unpredictable behavior when >using public vars? In light of this [1] comment it looks like you might run into trouble when using classes with public vars from within MXML. [1] http://apache-royale-development.20373.n8.nabble.com/Public-Vars-tp2698p27

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

See