Build failed in Jenkins: royale-asjs_MXTests #1155

See -- [...truncated 1000.35 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Build failed in Jenkins: royale-asjs_MXTests #1154

See -- [...truncated 999.57 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Build failed in Jenkins: royale-asjs_MXTests #1153

See -- [...truncated 1001.41 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Re: Question about stringifyNode

Thanks, Yeah I expected it to create mappings. I just wondered if it might create problems with offsets if the final output does not align with whatever happened during the original walk. I will investigate further as I get along with what I am doing. On Sat, Sep 14, 2019 at 11:20 AM Josh Tynja

Re: Question about stringifyNode

When I was first implementing source maps, I remember running into an issue where a use of stringifyNode() was messing them up. I don't remember the exact details, but I think I had to shift some of the logic around to get the mappings into the correct order. If that's right, then yes, stringifyNod

Re: Question about stringifyNode

sorry there is probably a write(s); in the middle there as well :) On Sat, Sep 14, 2019 at 11:08 AM Greg Dove wrote: > Josh, I think this is a question more for you... > > In terms of source mapping... is the 'stringifyNode' pattern that is used > in some places supported? > > For example > > s

Question about stringifyNode

Josh, I think this is a question more for you... In terms of source mapping... is the 'stringifyNode' pattern that is used in some places supported? For example s = stringifyNode(myNode); //<-walks and presumably creates mappings like normal write("("): //<-- some wrapper around 's' content (co

Build failed in Jenkins: royale-asjs_MXTests #1152

See -- [...truncated 1001.76 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Re: Discuss of release steps preparation

Hi, thanks Greg for bringing all that stuff. I completely forgot about all that improvements. I'm thinking that for Jewel there's many improvements. As well MX/Spark emulation have many ones too. I'll try to see if I can add some for Jewel. For MX/Spark emulation maybe others that worked on it sho

Re: Discuss of release steps preparation

I tested the installation (beta 10) and the subsequent steps using royale-cli and everything seems to be working. Thanks for all the fixes, Alex. Regards, Om On Fri, Sep 13, 2019 at 10:33 AM Greg Dove wrote: > Oh thanks, Josh! I will do that later today. > > > On Sat, Sep 14, 2019 at 5:32 AM J

Build failed in Jenkins: royale-asjs_MXTests #1151

See Changes: [piotrzarzycki21] jewel-slider: Make sliderTrackContainer protected to allow extending [piotrzarzycki21] jewel-slider: Missing COMPILE::JS for sliderTrackContainer f

Re: Discuss of release steps preparation

Oh thanks, Josh! I will do that later today. On Sat, Sep 14, 2019 at 5:32 AM Josh Tynjala wrote: > In royale-compiler, I already added my release notes from develop into > release/0.9.6. I simply forgot to do the same for royale-asjs. I added > that > line about RoyaleUnit just now. Go ahead an

Re: Discuss of release steps preparation

In royale-compiler, I already added my release notes from develop into release/0.9.6. I simply forgot to do the same for royale-asjs. I added that line about RoyaleUnit just now. Go ahead and add yours too, Greg. We'll be merging release/0.9.6 back into develop later, so if you put them directly in

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

See

Re: Discuss of release steps preparation

Hi Piotr, I'm not so familiar with the release process. Do you want additions to go directly into the release branch or should that be added to develop (assuming you would merge into release)? I see Josh added note about RoyalUnit in develop [1], which is not yet in release.[2] . So perhaps you w

Build failed in Jenkins: royale-asjs #2697

See Changes: [piotrzarzycki21] jewel-slider: Make sliderTrackContainer protected to allow extending -- [...truncated 1.78 MB...] [java] +env.A

Build failed in Jenkins: royale-asjs_MXTests #1150

See -- [...truncated 1001.31 KB...] [mxmlc] scanning for overrides: ObjectUtil [mxmlc] scanning for overrides: SolidBorderUtil [mxmlc] scanning

Discuss of release steps preparation

Hi Guys, I would like to cut RC1 again on Monday, so if anything should be tested or added please do so before Monday. Let me know if anything is against that. Thanks, Piotr On Fri, Sep 13, 2019, 12:32 AM Alex Harui wrote: > I pushed changes to update the config.xml files. It seemed to work