Re: Discuss of release steps preparation

[Piotr Zarzycki]

Hi,

It moved farther, but failed with different stacktrace [1]. I will try to
investigate this, unless someone has immediate idea why I got that issue.

[1] https://paste.apache.org/r48at

Thanks,
Piotr

śr., 4 wrz 2019 o 07:36 Alex Harui  napisał(a):

> FWIW, my Mac has:
>
> FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
> Debugger.app/Contents/MacOS/Flash Player Debugger'
>
> Note the single quotes instead of escaped spaces as described in the
> README.  I think some code in Ant or the compiler doesn't handle escaping
> spaces correctly.
>
> The point of having someone else be the RM is to debug the Ant scripts and
> other parts of the release process, and also to make sure at least one
> other person on this project knows how these scripts work and can help
> maintain them.  So even if you do get it working on Mac it will still mean
> that there is a bug in the process on Windows.  I could go try the scripts
> on Windows, but I'd rather see someone else learn how to debug these
> scripts.  I do not think I've seen any console output posted that might
> give a clue as to why those files get locked, nor have I seen any mention
> of modifying the scripts to add more debugging output around where Ant
> tasks get loaded.
>
> I haven't tried this myself, but there are supposedly tools to show what
> app has locked a file:
> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
>
> HTH,
> -Alex
>
> On 9/3/19, 2:27 PM, "Piotr Zarzycki"  wrote:
>
> Carlos,
>
> I have both, but I'm prime user on Windows. Mac is used only to test
> stuff
> ;)
>
> I have failed so many times on Windows so I decided configure stuff on
> Mac
> and try there.
>
> I will try tomorrow some of your tips.
>
> Thanks,
> Piotr
>
> On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr, sorry I didn't recall that you're on windows, not Mac. So
> all the
> > "Content" stuff is not valid, is something Mac related.
> >
> > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > ok it failed. How should I put in bash_profile file this path so
> it would
> > > be understandable?
> > >
> > > export
> > >
> > >
> >
> FLASHPLAYER_DEBUGGER=/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > Player Debugger
> > >
> > > On Windows we would probably go with:
> > >
> > >
> > >
> >
> FLASHPLAYER_DEBUGGER="/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > Player Debugger"
> > >
> > >
> > >
> > >
> > >
> > > wt., 3 wrz 2019 o 18:34 Piotr Zarzycki 
> > > napisał(a):
> > >
> > > > I have path exactly the same as Josh mention placed in bash
> script. I
> > > just
> > > > run build and will see whether this help. However after printenv
> I see
> > > that
> > > > path is cutted cause there are spaces in file name. On windows
> it would
> > > not
> > > > work, but maybe on it is different. We will see.
> > > >
> > > > wt., 3 wrz 2019 o 17:32 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > >> Hi Piotr, this is what I use in my .bash_profile:
> > > >>
> > > >> export FLASHPLAYER_DEBUGGER=/Applications/Flash\
> > > >> Player.app/Contents/MacOS/Flash\ Player\ Debugger
> > > >>
> > > >>
> > > >> El mar., 3 sept. 2019 a las 17:04, Piotr Zarzycki (<
> > > >> piotrzarzyck...@gmail.com>) escribió:
> > > >>
> > > >> > Hey Josh,
> > > >> >
> > > >> > Thank you so much! I will check it out soon.
> > > >> >
> > > >> > On Tue, Sep 3, 2019, 4:48 PM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > > >> > wrote:
> > > >> >
> > > >> > > I think you need to point to the executable inside of the
> .app
> > file.
> > > >> So
> > > >> > > it's something like this:
> > > >> > >
> > > >> > > /Applications/Flash Player.app/Contents/MacOS/Flash Player
> > Debugger
> > > >> > >
> > > >> > > I may not have that exactly right because I'm on Windows at
> the
> > > >> moment,
> > > >> > and
> > > >> > > I can't check. However, if you right-click the .app file,
> and
> > choose
> > > >> Show
> > > >> > > Package Contents, you can dig in there and find the correct
> path.
> > > >> > >
> > > >> > > --
> > > >> > > Josh Tynjala
> > > >> > > Bowler Hat LLC <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbowlerhat.dev&data=02%7C01%7Caharui%40adobe.com%7Ca1db4b177e7f4a8e1f1208d730b57629%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031428332586111&sdata=L0kadCJMUL5FLlvvHZyuZm2oOau%2BFBj0uX5nxGlgR9k%3D&reserved=0
> >
> > > >> > >
> > > >> > >
> > > >> > > On Tue, Sep 3, 2019 at 6:56 AM Piotr Zarzycki <
> > > >> piotrzarzyck...@gmail.com
> > > >

RE: Discuss of release steps preparation

[Yishay Weiss]

> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
>  
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
>  does not exist.



Is ANT_HOME env var defined?




From: Piotr Zarzycki 
Sent: Wednesday, September 4, 2019 11:24:09 AM
To: dev@royale.apache.org 
Subject: Re: Discuss of release steps preparation

Hi,

It moved farther, but failed with different stacktrace [1]. I will try to
investigate this, unless someone has immediate idea why I got that issue.

[1] https://paste.apache.org/r48at

Thanks,
Piotr

śr., 4 wrz 2019 o 07:36 Alex Harui  napisał(a):

> FWIW, my Mac has:
>
> FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
> Debugger.app/Contents/MacOS/Flash Player Debugger'
>
> Note the single quotes instead of escaped spaces as described in the
> README.  I think some code in Ant or the compiler doesn't handle escaping
> spaces correctly.
>
> The point of having someone else be the RM is to debug the Ant scripts and
> other parts of the release process, and also to make sure at least one
> other person on this project knows how these scripts work and can help
> maintain them.  So even if you do get it working on Mac it will still mean
> that there is a bug in the process on Windows.  I could go try the scripts
> on Windows, but I'd rather see someone else learn how to debug these
> scripts.  I do not think I've seen any console output posted that might
> give a clue as to why those files get locked, nor have I seen any mention
> of modifying the scripts to add more debugging output around where Ant
> tasks get loaded.
>
> I haven't tried this myself, but there are supposedly tools to show what
> app has locked a file:
> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
>
> HTH,
> -Alex
>
> On 9/3/19, 2:27 PM, "Piotr Zarzycki"  wrote:
>
> Carlos,
>
> I have both, but I'm prime user on Windows. Mac is used only to test
> stuff
> ;)
>
> I have failed so many times on Windows so I decided configure stuff on
> Mac
> and try there.
>
> I will try tomorrow some of your tips.
>
> Thanks,
> Piotr
>
> On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira 
> wrote:
>
> > Hi Piotr, sorry I didn't recall that you're on windows, not Mac. So
> all the
> > "Content" stuff is not valid, is something Mac related.
> >
> > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
> > piotrzarzyck...@gmail.com>) escribió:
> >
> > > ok it failed. How should I put in bash_profile file this path so
> it would
> > > be understandable?
> > >
> > > export
> > >
> > >
> >
> FLASHPLAYER_DEBUGGER=/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > Player Debugger
> > >
> > > On Windows we would probably go with:
> > >
> > >
> > >
> >
> FLASHPLAYER_DEBUGGER="/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > Player Debugger"
> > >
> > >
> > >
> > >
> > >
> > > wt., 3 wrz 2019 o 18:34 Piotr Zarzycki 
> > > napisał(a):
> > >
> > > > I have path exactly the same as Josh mention placed in bash
> script. I
> > > just
> > > > run build and will see whether this help. However after printenv
> I see
> > > that
> > > > path is cutted cause there are spaces in file name. On windows
> it would
> > > not
> > > > work, but maybe on it is different. We will see.
> > > >
> > > > wt., 3 wrz 2019 o 17:32 Carlos Rovira 
> > > > napisał(a):
> > > >
> > > >> Hi Piotr, this is what I use in my .bash_profile:
> > > >>
> > > >> export FLASHPLAYER_DEBUGGER=/Applications/Flash\
> > > >> Player.app/Contents/MacOS/Flash\ Player\ Debugger
> > > >>
> > > >>
> > > >> El mar., 3 sept. 2019 a las 17:04, Piotr Zarzycki (<
> > > >> piotrzarzyck...@gmail.com>) escribió:
> > > >>
> > > >> > Hey Josh,
> > > >> >
> > > >> > Thank you so much! I will check it out soon.
> > > >> >
> > > >> > On Tue, Sep 3, 2019, 4:48 PM Josh Tynjala <
> > joshtynj...@bowlerhat.dev>
> > > >> > wrote:
> > > >> >
> > > >> > > I think you need to point to the executable inside of the
> .app
> > file.
> > > >> So
> > > >> > > it's something like this:
> > > >> > >
> > > >> > > /Applications/Flash Player.app/Contents/MacOS/Flash Player
> > Debugger
> > > >> > >
> > > >> > > I may not have that exactly right because I'm on Windows at
> the
> > > >> moment,
> > > >> > and
> > > >> > > I can't check. However, if you right-click the .app file,
> and
> > choose
> > > >> Show
> > > >> > > Package Contents, you can dig in there and find the correct
> path.
> > > >> > >
> > > >> > > --
> > > >> > > Josh Tynjala
> > > >> > > Bowler Hat LLC <
> https:

Re: Discuss of release steps preparation

[Piotr Zarzycki]

Hi Yishay,

It was pretty stupid from my sight. I was certain that I have this env
variable setup, cause ant is working for me. I have no idea how. Let me set
it and see whether it help.

Thanks,
Piotr

śr., 4 wrz 2019 o 10:37 Yishay Weiss  napisał(a):

> >
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
> does not exist.
>
>
>
> Is ANT_HOME env var defined?
>
>
>
> 
> From: Piotr Zarzycki 
> Sent: Wednesday, September 4, 2019 11:24:09 AM
> To: dev@royale.apache.org 
> Subject: Re: Discuss of release steps preparation
>
> Hi,
>
> It moved farther, but failed with different stacktrace [1]. I will try to
> investigate this, unless someone has immediate idea why I got that issue.
>
> [1] https://paste.apache.org/r48at
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 07:36 Alex Harui  napisał(a):
>
> > FWIW, my Mac has:
> >
> > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
> > Debugger.app/Contents/MacOS/Flash Player Debugger'
> >
> > Note the single quotes instead of escaped spaces as described in the
> > README.  I think some code in Ant or the compiler doesn't handle escaping
> > spaces correctly.
> >
> > The point of having someone else be the RM is to debug the Ant scripts
> and
> > other parts of the release process, and also to make sure at least one
> > other person on this project knows how these scripts work and can help
> > maintain them.  So even if you do get it working on Mac it will still
> mean
> > that there is a bug in the process on Windows.  I could go try the
> scripts
> > on Windows, but I'd rather see someone else learn how to debug these
> > scripts.  I do not think I've seen any console output posted that might
> > give a clue as to why those files get locked, nor have I seen any mention
> > of modifying the scripts to add more debugging output around where Ant
> > tasks get loaded.
> >
> > I haven't tried this myself, but there are supposedly tools to show what
> > app has locked a file:
> >
> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
> >
> > HTH,
> > -Alex
> >
> > On 9/3/19, 2:27 PM, "Piotr Zarzycki"  wrote:
> >
> > Carlos,
> >
> > I have both, but I'm prime user on Windows. Mac is used only to test
> > stuff
> > ;)
> >
> > I have failed so many times on Windows so I decided configure stuff
> on
> > Mac
> > and try there.
> >
> > I will try tomorrow some of your tips.
> >
> > Thanks,
> > Piotr
> >
> > On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr, sorry I didn't recall that you're on windows, not Mac. So
> > all the
> > > "Content" stuff is not valid, is something Mac related.
> > >
> > > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > ok it failed. How should I put in bash_profile file this path so
> > it would
> > > > be understandable?
> > > >
> > > > export
> > > >
> > > >
> > >
> >
> FLASHPLAYER_DEBUGGER=/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > > Player Debugger
> > > >
> > > > On Windows we would probably go with:
> > > >
> > > >
> > > >
> > >
> >
> FLASHPLAYER_DEBUGGER="/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > > Player Debugger"
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > wt., 3 wrz 2019 o 18:34 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > I have path exactly the same as Josh mention placed in bash
> > script. I
> > > > just
> > > > > run build and will see whether this help. However after
> printenv
> > I see
> > > > that
> > > > > path is cutted cause there are spaces in file name. On windows
> > it would
> > > > not
> > > > > work, but maybe on it is different. We will see.
> > > > >
> > > > > wt., 3 wrz 2019 o 17:32 Carlos Rovira  >
> > > > > napisał(a):
> > > > >
> > > > >> Hi Piotr, this is what I use in my .bash_profile:
> > > > >>
> > > > >> export FLASHPLAYER_DEBUGGER=/Applications/Flash\
> > > > >> Player.app/Contents/MacOS/Flash\ Player\ Debugger
> > > > >>
> > > > >>
> > > > >> El mar., 3 sept. 2019 a las 17:04, Piotr Zarzycki (<
> > > > >> piotrzarzyck...@gmail.com>) escribió:
> > > > >>
> > > > >> > Hey Josh,
> > > > >> >
> > > > >> > Thank you so much! I will check it out soon.
> > > > >> >
> > > > >> > On Tue, Sep 3, 2019, 4:48 PM Josh Tynjala <
> > > joshtynj...@bowlerhat.dev>
> > > > >> > wrote:
> > > > >> >
> > > > >> > > I think you need to point to the executable inside of the
> > .app
> > > file.
> > > > >> So
> > > > >> > > it's somethin

RE: Discuss of release steps preparation

[Yishay Weiss]

Here’s what I’ve got.



ANT_HOME

C:\dev\ant\apache-ant-1.10.1




From: Piotr Zarzycki 
Sent: Wednesday, September 4, 2019 11:56:02 AM
To: dev@royale.apache.org 
Subject: Re: Discuss of release steps preparation

Hi Yishay,

It was pretty stupid from my sight. I was certain that I have this env
variable setup, cause ant is working for me. I have no idea how. Let me set
it and see whether it help.

Thanks,
Piotr

śr., 4 wrz 2019 o 10:37 Yishay Weiss  napisał(a):

> >
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
> does not exist.
>
>
>
> Is ANT_HOME env var defined?
>
>
>
> 
> From: Piotr Zarzycki 
> Sent: Wednesday, September 4, 2019 11:24:09 AM
> To: dev@royale.apache.org 
> Subject: Re: Discuss of release steps preparation
>
> Hi,
>
> It moved farther, but failed with different stacktrace [1]. I will try to
> investigate this, unless someone has immediate idea why I got that issue.
>
> [1] https://paste.apache.org/r48at
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 07:36 Alex Harui  napisał(a):
>
> > FWIW, my Mac has:
> >
> > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
> > Debugger.app/Contents/MacOS/Flash Player Debugger'
> >
> > Note the single quotes instead of escaped spaces as described in the
> > README.  I think some code in Ant or the compiler doesn't handle escaping
> > spaces correctly.
> >
> > The point of having someone else be the RM is to debug the Ant scripts
> and
> > other parts of the release process, and also to make sure at least one
> > other person on this project knows how these scripts work and can help
> > maintain them.  So even if you do get it working on Mac it will still
> mean
> > that there is a bug in the process on Windows.  I could go try the
> scripts
> > on Windows, but I'd rather see someone else learn how to debug these
> > scripts.  I do not think I've seen any console output posted that might
> > give a clue as to why those files get locked, nor have I seen any mention
> > of modifying the scripts to add more debugging output around where Ant
> > tasks get loaded.
> >
> > I haven't tried this myself, but there are supposedly tools to show what
> > app has locked a file:
> >
> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
> >
> > HTH,
> > -Alex
> >
> > On 9/3/19, 2:27 PM, "Piotr Zarzycki"  wrote:
> >
> > Carlos,
> >
> > I have both, but I'm prime user on Windows. Mac is used only to test
> > stuff
> > ;)
> >
> > I have failed so many times on Windows so I decided configure stuff
> on
> > Mac
> > and try there.
> >
> > I will try tomorrow some of your tips.
> >
> > Thanks,
> > Piotr
> >
> > On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira 
> > wrote:
> >
> > > Hi Piotr, sorry I didn't recall that you're on windows, not Mac. So
> > all the
> > > "Content" stuff is not valid, is something Mac related.
> > >
> > > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
> > > piotrzarzyck...@gmail.com>) escribió:
> > >
> > > > ok it failed. How should I put in bash_profile file this path so
> > it would
> > > > be understandable?
> > > >
> > > > export
> > > >
> > > >
> > >
> >
> FLASHPLAYER_DEBUGGER=/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > > Player Debugger
> > > >
> > > > On Windows we would probably go with:
> > > >
> > > >
> > > >
> > >
> >
> FLASHPLAYER_DEBUGGER="/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > > Player Debugger"
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > wt., 3 wrz 2019 o 18:34 Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> > > > napisał(a):
> > > >
> > > > > I have path exactly the same as Josh mention placed in bash
> > script. I
> > > > just
> > > > > run build and will see whether this help. However after
> printenv
> > I see
> > > > that
> > > > > path is cutted cause there are spaces in file name. On windows
> > it would
> > > > not
> > > > > work, but maybe on it is different. We will see.
> > > > >
> > > > > wt., 3 wrz 2019 o 17:32 Carlos Rovira  >
> > > > > napisał(a):
> > > > >
> > > > >> Hi Piotr, this is what I use in my .bash_profile:
> > > > >>
> > > > >> export FLASHPLAYER_DEBUGGER=/Applications/Flash\
> > > > >> Player.app/Contents/MacOS/Flash\ Player\ Debugger
> > > > >>
> > > > >>
> > > > >> El mar., 3 sept. 2019 a las 17:04, Piotr Zarzycki (<
> > > > >> piotrzarzyck...@gmail.com>) escribió:
> > > > >>
> > > > >> > Hey Josh,
> > > > >> >
> > > > >> > Thank you so much! I will check it out soon.
> > > > >> >
> > > > >> > On Tue, Sep 3, 2019, 4:48 P

Heads up on XML

[Greg Dove]

This is particularly for Harbs and Yishay, as I think you are both (or both
have been) using XML quite a bit. I have quite a few  fixes coming. All
with tests that match on swf and js.

I am currently working to demonstrate proof of concept to a prospective
client for migration of a Flex app. The app makes extensive use of e4x and
uses a bunch of features that I expect had not received attention
previously, because they were originally either not working with the
codebase I am porting, or i think some even caused errors in the javascript
output.

So I have spent the last several days almost full time figuring things out
and working on fixes, between the compiler and emulation classes.
All the previous XML tests continue to pass, but I have many more unit
tests and fixes lined up for the following:

namespace directives
default xml namespace
use namespace (multiple)

a number of fixes for xml filtering, including:
-'this' resolves correctly in filters that include external references from
the fitler expression to the 'this' scope
-handles alternate ordering of comparisons between XML 'getters' and
literals
e.g. something.(name() = "cat")  or something.("cat" = name()) (these are
the same)
-it (will) now handle XML e4x references in nested function calls inside
the filter, e.g. things like:
e.g.
var people:XML = 

Bob
32


Joe
46

;
 var findJoeByAge:Function = function (i:int):Boolean {
return i > 40;
};
people.person.(findJoeByAge(parseInt(age))).name


I have lots more granular tests in QName, Namespace, and XML with tuning to
improve reliability.
toXMLString XML node output also matches flash more correctly in what I
have coming.

One thing that I am trying to figure out, which I would appreciate input on
if someone has an answer:
For the example:

var feed:XML = new XML(
'http://www.w3.org/2005/Atom";
xmlns:m="nothing">\n' +
'  \n' +
'\n');
var atomSpace:Namespace = new Namespace('http://www.w3.org/2005/Atom');

Can anyone explain why this (in SWF, as a reference implementation):
trace(feed.atomSpace::link.length())
trace(feed.atomSpace::link.toXMLString())
//output:
0
{empty string}
is different to:
trace(feed.child(new QName(atomSpace,'link')).length())
trace(feed.child(new QName(atomSpace,'link')).toXMLString())
//output:
1
http://www.w3.org/2005/Atom"; xmlns:m="nothing"/>

I had assumed the above cases would be the same, but the second one is
behaving as if it has the default namespace included with the specified
namespace in the QName matching (it does correctly match the namespace
specifically as well -with e.g. 

Re: Discuss of release steps preparation

[Piotr Zarzycki]

I was able to produce ant artifacts on Mac! I will try get an RC1 today.

śr., 4 wrz 2019 o 11:11 Yishay Weiss  napisał(a):

> Here’s what I’ve got.
>
>
>
> ANT_HOME
>
> C:\dev\ant\apache-ant-1.10.1
>
>
>
> 
> From: Piotr Zarzycki 
> Sent: Wednesday, September 4, 2019 11:56:02 AM
> To: dev@royale.apache.org 
> Subject: Re: Discuss of release steps preparation
>
> Hi Yishay,
>
> It was pretty stupid from my sight. I was certain that I have this env
> variable setup, cause ant is working for me. I have no idea how. Let me set
> it and see whether it help.
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 10:37 Yishay Weiss  napisał(a):
>
> > >
> >
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
> >
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
> > does not exist.
> >
> >
> >
> > Is ANT_HOME env var defined?
> >
> >
> >
> > 
> > From: Piotr Zarzycki 
> > Sent: Wednesday, September 4, 2019 11:24:09 AM
> > To: dev@royale.apache.org 
> > Subject: Re: Discuss of release steps preparation
> >
> > Hi,
> >
> > It moved farther, but failed with different stacktrace [1]. I will try to
> > investigate this, unless someone has immediate idea why I got that issue.
> >
> > [1] https://paste.apache.org/r48at
> >
> > Thanks,
> > Piotr
> >
> > śr., 4 wrz 2019 o 07:36 Alex Harui 
> napisał(a):
> >
> > > FWIW, my Mac has:
> > >
> > > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
> > > Debugger.app/Contents/MacOS/Flash Player Debugger'
> > >
> > > Note the single quotes instead of escaped spaces as described in the
> > > README.  I think some code in Ant or the compiler doesn't handle
> escaping
> > > spaces correctly.
> > >
> > > The point of having someone else be the RM is to debug the Ant scripts
> > and
> > > other parts of the release process, and also to make sure at least one
> > > other person on this project knows how these scripts work and can help
> > > maintain them.  So even if you do get it working on Mac it will still
> > mean
> > > that there is a bug in the process on Windows.  I could go try the
> > scripts
> > > on Windows, but I'd rather see someone else learn how to debug these
> > > scripts.  I do not think I've seen any console output posted that might
> > > give a clue as to why those files get locked, nor have I seen any
> mention
> > > of modifying the scripts to add more debugging output around where Ant
> > > tasks get loaded.
> > >
> > > I haven't tried this myself, but there are supposedly tools to show
> what
> > > app has locked a file:
> > >
> >
> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
> > >
> > > HTH,
> > > -Alex
> > >
> > > On 9/3/19, 2:27 PM, "Piotr Zarzycki" 
> wrote:
> > >
> > > Carlos,
> > >
> > > I have both, but I'm prime user on Windows. Mac is used only to
> test
> > > stuff
> > > ;)
> > >
> > > I have failed so many times on Windows so I decided configure stuff
> > on
> > > Mac
> > > and try there.
> > >
> > > I will try tomorrow some of your tips.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira <
> carlosrov...@apache.org>
> > > wrote:
> > >
> > > > Hi Piotr, sorry I didn't recall that you're on windows, not Mac.
> So
> > > all the
> > > > "Content" stuff is not valid, is something Mac related.
> > > >
> > > > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
> > > > piotrzarzyck...@gmail.com>) escribió:
> > > >
> > > > > ok it failed. How should I put in bash_profile file this path
> so
> > > it would
> > > > > be understandable?
> > > > >
> > > > > export
> > > > >
> > > > >
> > > >
> > >
> >
> FLASHPLAYER_DEBUGGER=/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > > > Player Debugger
> > > > >
> > > > > On Windows we would probably go with:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
> FLASHPLAYER_DEBUGGER="/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
> > > > > Player Debugger"
> > > > >
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > wt., 3 wrz 2019 o 18:34 Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > > > > napisał(a):
> > > > >
> > > > > > I have path exactly the same as Josh mention placed in bash
> > > script. I
> > > > > just
> > > > > > run build and will see whether this help. However after
> > printenv
> > > I see
> > > > > that
> > > > > > path is cutted cause there are spaces in file name. On
> windows
> > > it would
> > > > > not
> > > > > > work, but maybe on it is different. We will see.
> > > > > >
> > > > > > wt., 3 wrz 2019 o 17:32 Carlos Rovira <
> carlosrov...@apache.org
> > >
> > > > > > napisał(a):
> > > > > >
> > > > > >> Hi Piot

Build failed in Jenkins: royale-asjs_MXTests #1120

[Apache Royale CI Server]

See 


--
[...truncated 968.90 KB...]
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout
[mxmlc] scanning for overrides: IBinaryDataInput
  

Re: Discuss of release steps preparation

[Piotr Zarzycki]

It looks like I have another problems. Target for uploading ant artifacts
is failing:

ant -f releasesteps_asjs.xml Release_Step_013_Upload
-Drelease.version=0.9.6 -Drc=1

Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml

check-name-and-svn:
 [echo] Name: 'Piotr Zarzycki'
 [echo] svn.dist.dev: /Users/piotr/Downloads/royale/dist/dev
 [echo] svn.dist.release: /Users/piotr/Downloads/royale/dist/release
 [echo] svn: /usr/bin/svn

BUILD FAILED
/Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The svn.dist.dev
property is not set to the working copy for
https://dist.apache.org/repos/dist/dev.

As you can see above I have all properties setup cause I made an echo. I
don't understand what is happening...

Thanks,
Piotr

śr., 4 wrz 2019 o 13:13 Piotr Zarzycki 
napisał(a):

> I was able to produce ant artifacts on Mac! I will try get an RC1 today.
>
> śr., 4 wrz 2019 o 11:11 Yishay Weiss  napisał(a):
>
>> Here’s what I’ve got.
>>
>>
>>
>> ANT_HOME
>>
>> C:\dev\ant\apache-ant-1.10.1
>>
>>
>>
>> 
>> From: Piotr Zarzycki 
>> Sent: Wednesday, September 4, 2019 11:56:02 AM
>> To: dev@royale.apache.org 
>> Subject: Re: Discuss of release steps preparation
>>
>> Hi Yishay,
>>
>> It was pretty stupid from my sight. I was certain that I have this env
>> variable setup, cause ant is working for me. I have no idea how. Let me
>> set
>> it and see whether it help.
>>
>> Thanks,
>> Piotr
>>
>> śr., 4 wrz 2019 o 10:37 Yishay Weiss  napisał(a):
>>
>> > >
>> >
>> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
>> >
>> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
>> > does not exist.
>> >
>> >
>> >
>> > Is ANT_HOME env var defined?
>> >
>> >
>> >
>> > 
>> > From: Piotr Zarzycki 
>> > Sent: Wednesday, September 4, 2019 11:24:09 AM
>> > To: dev@royale.apache.org 
>> > Subject: Re: Discuss of release steps preparation
>> >
>> > Hi,
>> >
>> > It moved farther, but failed with different stacktrace [1]. I will try
>> to
>> > investigate this, unless someone has immediate idea why I got that
>> issue.
>> >
>> > [1] https://paste.apache.org/r48at
>> >
>> > Thanks,
>> > Piotr
>> >
>> > śr., 4 wrz 2019 o 07:36 Alex Harui 
>> napisał(a):
>> >
>> > > FWIW, my Mac has:
>> > >
>> > > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
>> > > Debugger.app/Contents/MacOS/Flash Player Debugger'
>> > >
>> > > Note the single quotes instead of escaped spaces as described in the
>> > > README.  I think some code in Ant or the compiler doesn't handle
>> escaping
>> > > spaces correctly.
>> > >
>> > > The point of having someone else be the RM is to debug the Ant scripts
>> > and
>> > > other parts of the release process, and also to make sure at least one
>> > > other person on this project knows how these scripts work and can help
>> > > maintain them.  So even if you do get it working on Mac it will still
>> > mean
>> > > that there is a bug in the process on Windows.  I could go try the
>> > scripts
>> > > on Windows, but I'd rather see someone else learn how to debug these
>> > > scripts.  I do not think I've seen any console output posted that
>> might
>> > > give a clue as to why those files get locked, nor have I seen any
>> mention
>> > > of modifying the scripts to add more debugging output around where Ant
>> > > tasks get loaded.
>> > >
>> > > I haven't tried this myself, but there are supposedly tools to show
>> what
>> > > app has locked a file:
>> > >
>> >
>> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
>> > >
>> > > HTH,
>> > > -Alex
>> > >
>> > > On 9/3/19, 2:27 PM, "Piotr Zarzycki" 
>> wrote:
>> > >
>> > > Carlos,
>> > >
>> > > I have both, but I'm prime user on Windows. Mac is used only to
>> test
>> > > stuff
>> > > ;)
>> > >
>> > > I have failed so many times on Windows so I decided configure
>> stuff
>> > on
>> > > Mac
>> > > and try there.
>> > >
>> > > I will try tomorrow some of your tips.
>> > >
>> > > Thanks,
>> > > Piotr
>> > >
>> > > On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira <
>> carlosrov...@apache.org>
>> > > wrote:
>> > >
>> > > > Hi Piotr, sorry I didn't recall that you're on windows, not
>> Mac. So
>> > > all the
>> > > > "Content" stuff is not valid, is something Mac related.
>> > > >
>> > > > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
>> > > > piotrzarzyck...@gmail.com>) escribió:
>> > > >
>> > > > > ok it failed. How should I put in bash_profile file this path
>> so
>> > > it would
>> > > > > be understandable?
>> > > > >
>> > > > > export
>> > > > >
>> > > > >
>> > > >
>> > >
>> >
>> FLASHPLAYER_DEBUGGER=/Users/piotr/Downloads/player/flashplayer.app/Contents/MacOS/Flash
>> > > > > Player Debugger
>> > > > >
>> > > > > On Windows we would pro

Re: Discuss of release steps preparation

[Piotr Zarzycki]

>From that point I will probably upload artifacts manually and run RC1.

śr., 4 wrz 2019 o 16:30 Piotr Zarzycki 
napisał(a):

> It looks like I have another problems. Target for uploading ant artifacts
> is failing:
>
> ant -f releasesteps_asjs.xml Release_Step_013_Upload
> -Drelease.version=0.9.6 -Drc=1
>
> Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml
>
> check-name-and-svn:
>  [echo] Name: 'Piotr Zarzycki'
>  [echo] svn.dist.dev: /Users/piotr/Downloads/royale/dist/dev
>  [echo] svn.dist.release: /Users/piotr/Downloads/royale/dist/release
>  [echo] svn: /usr/bin/svn
>
> BUILD FAILED
> /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The svn.dist.dev
> property is not set to the working copy for
> https://dist.apache.org/repos/dist/dev.
>
> As you can see above I have all properties setup cause I made an echo. I
> don't understand what is happening...
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 13:13 Piotr Zarzycki 
> napisał(a):
>
>> I was able to produce ant artifacts on Mac! I will try get an RC1 today.
>>
>> śr., 4 wrz 2019 o 11:11 Yishay Weiss  napisał(a):
>>
>>> Here’s what I’ve got.
>>>
>>>
>>>
>>> ANT_HOME
>>>
>>> C:\dev\ant\apache-ant-1.10.1
>>>
>>>
>>>
>>> 
>>> From: Piotr Zarzycki 
>>> Sent: Wednesday, September 4, 2019 11:56:02 AM
>>> To: dev@royale.apache.org 
>>> Subject: Re: Discuss of release steps preparation
>>>
>>> Hi Yishay,
>>>
>>> It was pretty stupid from my sight. I was certain that I have this env
>>> variable setup, cause ant is working for me. I have no idea how. Let me
>>> set
>>> it and see whether it help.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> śr., 4 wrz 2019 o 10:37 Yishay Weiss 
>>> napisał(a):
>>>
>>> > >
>>> >
>>> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
>>> >
>>> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
>>> > does not exist.
>>> >
>>> >
>>> >
>>> > Is ANT_HOME env var defined?
>>> >
>>> >
>>> >
>>> > 
>>> > From: Piotr Zarzycki 
>>> > Sent: Wednesday, September 4, 2019 11:24:09 AM
>>> > To: dev@royale.apache.org 
>>> > Subject: Re: Discuss of release steps preparation
>>> >
>>> > Hi,
>>> >
>>> > It moved farther, but failed with different stacktrace [1]. I will try
>>> to
>>> > investigate this, unless someone has immediate idea why I got that
>>> issue.
>>> >
>>> > [1] https://paste.apache.org/r48at
>>> >
>>> > Thanks,
>>> > Piotr
>>> >
>>> > śr., 4 wrz 2019 o 07:36 Alex Harui 
>>> napisał(a):
>>> >
>>> > > FWIW, my Mac has:
>>> > >
>>> > > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
>>> > > Debugger.app/Contents/MacOS/Flash Player Debugger'
>>> > >
>>> > > Note the single quotes instead of escaped spaces as described in the
>>> > > README.  I think some code in Ant or the compiler doesn't handle
>>> escaping
>>> > > spaces correctly.
>>> > >
>>> > > The point of having someone else be the RM is to debug the Ant
>>> scripts
>>> > and
>>> > > other parts of the release process, and also to make sure at least
>>> one
>>> > > other person on this project knows how these scripts work and can
>>> help
>>> > > maintain them.  So even if you do get it working on Mac it will still
>>> > mean
>>> > > that there is a bug in the process on Windows.  I could go try the
>>> > scripts
>>> > > on Windows, but I'd rather see someone else learn how to debug these
>>> > > scripts.  I do not think I've seen any console output posted that
>>> might
>>> > > give a clue as to why those files get locked, nor have I seen any
>>> mention
>>> > > of modifying the scripts to add more debugging output around where
>>> Ant
>>> > > tasks get loaded.
>>> > >
>>> > > I haven't tried this myself, but there are supposedly tools to show
>>> what
>>> > > app has locked a file:
>>> > >
>>> >
>>> https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder
>>> > >
>>> > > HTH,
>>> > > -Alex
>>> > >
>>> > > On 9/3/19, 2:27 PM, "Piotr Zarzycki" 
>>> wrote:
>>> > >
>>> > > Carlos,
>>> > >
>>> > > I have both, but I'm prime user on Windows. Mac is used only to
>>> test
>>> > > stuff
>>> > > ;)
>>> > >
>>> > > I have failed so many times on Windows so I decided configure
>>> stuff
>>> > on
>>> > > Mac
>>> > > and try there.
>>> > >
>>> > > I will try tomorrow some of your tips.
>>> > >
>>> > > Thanks,
>>> > > Piotr
>>> > >
>>> > > On Tue, Sep 3, 2019, 7:39 PM Carlos Rovira <
>>> carlosrov...@apache.org>
>>> > > wrote:
>>> > >
>>> > > > Hi Piotr, sorry I didn't recall that you're on windows, not
>>> Mac. So
>>> > > all the
>>> > > > "Content" stuff is not valid, is something Mac related.
>>> > > >
>>> > > > El mar., 3 sept. 2019 a las 18:50, Piotr Zarzycki (<
>>> > > > piotrzarzyck...@gmail.com>) escribió:
>>> > > >
>>> > > > > ok it failed. How should I put in bash_profile file thi

Re: Heads up on XML

[Alex Harui]

Don't know.  Have you rummaged through the spec?
https://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/Ecma-357.pdf

HTH,
-Alex

On 9/4/19, 3:11 AM, "Greg Dove"  wrote:

This is particularly for Harbs and Yishay, as I think you are both (or both
have been) using XML quite a bit. I have quite a few  fixes coming. All
with tests that match on swf and js.

I am currently working to demonstrate proof of concept to a prospective
client for migration of a Flex app. The app makes extensive use of e4x and
uses a bunch of features that I expect had not received attention
previously, because they were originally either not working with the
codebase I am porting, or i think some even caused errors in the javascript
output.

So I have spent the last several days almost full time figuring things out
and working on fixes, between the compiler and emulation classes.
All the previous XML tests continue to pass, but I have many more unit
tests and fixes lined up for the following:

namespace directives
default xml namespace
use namespace (multiple)

a number of fixes for xml filtering, including:
-'this' resolves correctly in filters that include external references from
the fitler expression to the 'this' scope
-handles alternate ordering of comparisons between XML 'getters' and
literals
e.g. something.(name() = "cat")  or something.("cat" = name()) (these are
the same)
-it (will) now handle XML e4x references in nested function calls inside
the filter, e.g. things like:
e.g.
var people:XML = 

Bob
32


Joe
46

;
 var findJoeByAge:Function = function (i:int):Boolean {
return i > 40;
};
people.person.(findJoeByAge(parseInt(age))).name


I have lots more granular tests in QName, Namespace, and XML with tuning to
improve reliability.
toXMLString XML node output also matches flash more correctly in what I
have coming.

One thing that I am trying to figure out, which I would appreciate input on
if someone has an answer:
For the example:

var feed:XML = new XML(
'https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C4fc6b31478da4718992c08d7312038b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031886769375971&sdata=YxDoQRD0NhfUfCK1QWIazLqeiP7vNRFFCaOLFF1NIow%3D&reserved=0";
xmlns:m="nothing">\n' +
'  \n' +
'\n');
var atomSpace:Namespace = new 
Namespace('https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C4fc6b31478da4718992c08d7312038b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031886769375971&sdata=YxDoQRD0NhfUfCK1QWIazLqeiP7vNRFFCaOLFF1NIow%3D&reserved=0');

Can anyone explain why this (in SWF, as a reference implementation):
trace(feed.atomSpace::link.length())
trace(feed.atomSpace::link.toXMLString())
//output:
0
{empty string}
is different to:
trace(feed.child(new QName(atomSpace,'link')).length())
trace(feed.child(new QName(atomSpace,'link')).toXMLString())
//output:
1
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C4fc6b31478da4718992c08d7312038b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031886769375971&sdata=YxDoQRD0NhfUfCK1QWIazLqeiP7vNRFFCaOLFF1NIow%3D&reserved=0";
 xmlns:m="nothing"/>

I had assumed the above cases would be the same, but the second one is
behaving as if it has the default namespace included with the specified
namespace in the QName matching (it does correctly match the namespace
specifically as well -with e.g. 

Re: Discuss of release steps preparation

[Alex Harui]

Again, the goal is here to debug the scripts, not to skip them.

And it is hard to help without console output to examine.

Yes, you have set the variables, but have the other steps run that generate an 
SVN working copy at that destination?  Show the console output related to it.

HTH,
-Alex

On 9/4/19, 9:01 AM, "Piotr Zarzycki"  wrote:

From that point I will probably upload artifacts manually and run RC1.

śr., 4 wrz 2019 o 16:30 Piotr Zarzycki 
napisał(a):

> It looks like I have another problems. Target for uploading ant artifacts
> is failing:
>
> ant -f releasesteps_asjs.xml Release_Step_013_Upload
> -Drelease.version=0.9.6 -Drc=1
>
> Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml
>
> check-name-and-svn:
>  [echo] Name: 'Piotr Zarzycki'
>  [echo] svn.dist.dev: /Users/piotr/Downloads/royale/dist/dev
>  [echo] svn.dist.release: /Users/piotr/Downloads/royale/dist/release
>  [echo] svn: /usr/bin/svn
>
> BUILD FAILED
> /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The svn.dist.dev
> property is not set to the working copy for
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev&data=02%7C01%7Caharui%40adobe.com%7C4e25cee076954707866508d731511a64%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032096735701135&sdata=5fZN5a4KNvVznt%2B7QTEXIAhUg0UxwYJzDLCnKfm%2B9pM%3D&reserved=0.
>
> As you can see above I have all properties setup cause I made an echo. I
> don't understand what is happening...
>
> Thanks,
> Piotr
>
> śr., 4 wrz 2019 o 13:13 Piotr Zarzycki 
> napisał(a):
>
>> I was able to produce ant artifacts on Mac! I will try get an RC1 today.
>>
>> śr., 4 wrz 2019 o 11:11 Yishay Weiss  napisał(a):
>>
>>> Here’s what I’ve got.
>>>
>>>
>>>
>>> ANT_HOME
>>>
>>> C:\dev\ant\apache-ant-1.10.1
>>>
>>>
>>>
>>> 
>>> From: Piotr Zarzycki 
>>> Sent: Wednesday, September 4, 2019 11:56:02 AM
>>> To: dev@royale.apache.org 
>>> Subject: Re: Discuss of release steps preparation
>>>
>>> Hi Yishay,
>>>
>>> It was pretty stupid from my sight. I was certain that I have this env
>>> variable setup, cause ant is working for me. I have no idea how. Let me
>>> set
>>> it and see whether it help.
>>>
>>> Thanks,
>>> Piotr
>>>
>>> śr., 4 wrz 2019 o 10:37 Yishay Weiss 
>>> napisał(a):
>>>
>>> > >
>>> >
>>> 
/Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
>>> >
>>> 
/Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
>>> > does not exist.
>>> >
>>> >
>>> >
>>> > Is ANT_HOME env var defined?
>>> >
>>> >
>>> >
>>> > 
>>> > From: Piotr Zarzycki 
>>> > Sent: Wednesday, September 4, 2019 11:24:09 AM
>>> > To: dev@royale.apache.org 
>>> > Subject: Re: Discuss of release steps preparation
>>> >
>>> > Hi,
>>> >
>>> > It moved farther, but failed with different stacktrace [1]. I will try
>>> to
>>> > investigate this, unless someone has immediate idea why I got that
>>> issue.
>>> >
>>> > [1] 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fr48at&data=02%7C01%7Caharui%40adobe.com%7C4e25cee076954707866508d731511a64%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032096735701135&sdata=kqeCxKyMxz%2BZJuyDByWfU4Sp6mCRVIbr7bdK5GKFDr0%3D&reserved=0
>>> >
>>> > Thanks,
>>> > Piotr
>>> >
>>> > śr., 4 wrz 2019 o 07:36 Alex Harui 
>>> napisał(a):
>>> >
>>> > > FWIW, my Mac has:
>>> > >
>>> > > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
>>> > > Debugger.app/Contents/MacOS/Flash Player Debugger'
>>> > >
>>> > > Note the single quotes instead of escaped spaces as described in the
>>> > > README.  I think some code in Ant or the compiler doesn't handle
>>> escaping
>>> > > spaces correctly.
>>> > >
>>> > > The point of having someone else be the RM is to debug the Ant
>>> scripts
>>> > and
>>> > > other parts of the release process, and also to make sure at least
>>> one
>>> > > other person on this project knows how these scripts work and can
>>> help
>>> > > maintain them.  So even if you do get it working on Mac it will 
still
>>> > mean
>>> > > that there is a bug in the process on Windows.  I could go try the
>>> > scripts
>>> > > on Windows, but I'd rather see someone else learn how to debug these
>>> > > scripts.  I do not think I've seen any console output posted that
>>> might
>>> > > give a clue as to why those files get locked, nor have I seen any
>>> mention

Re: Discuss of release steps preparation

[Piotr Zarzycki]

Hi Alex,

I know that is the goal, but I simply failed to meet those goals and I gave
up on that. I have artifacts and I would like to release Royale - that's
may goal, whether I do this in 90% automatically and 10% manually after so
many hours of work it doesn't matter to me now.

You are seeing full console output actually. Nothing more happen there.

Thanks,
Piotr

śr., 4 wrz 2019 o 18:11 Alex Harui  napisał(a):

> Again, the goal is here to debug the scripts, not to skip them.
>
> And it is hard to help without console output to examine.
>
> Yes, you have set the variables, but have the other steps run that
> generate an SVN working copy at that destination?  Show the console output
> related to it.
>
> HTH,
> -Alex
>
> On 9/4/19, 9:01 AM, "Piotr Zarzycki"  wrote:
>
> From that point I will probably upload artifacts manually and run RC1.
>
> śr., 4 wrz 2019 o 16:30 Piotr Zarzycki 
> napisał(a):
>
> > It looks like I have another problems. Target for uploading ant
> artifacts
> > is failing:
> >
> > ant -f releasesteps_asjs.xml Release_Step_013_Upload
> > -Drelease.version=0.9.6 -Drc=1
> >
> > Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml
> >
> > check-name-and-svn:
> >  [echo] Name: 'Piotr Zarzycki'
> >  [echo] svn.dist.dev: /Users/piotr/Downloads/royale/dist/dev
> >  [echo] svn.dist.release:
> /Users/piotr/Downloads/royale/dist/release
> >  [echo] svn: /usr/bin/svn
> >
> > BUILD FAILED
> > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The
> svn.dist.dev
> > property is not set to the working copy for
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev&data=02%7C01%7Caharui%40adobe.com%7C4e25cee076954707866508d731511a64%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032096735701135&sdata=5fZN5a4KNvVznt%2B7QTEXIAhUg0UxwYJzDLCnKfm%2B9pM%3D&reserved=0
> .
> >
> > As you can see above I have all properties setup cause I made an
> echo. I
> > don't understand what is happening...
> >
> > Thanks,
> > Piotr
> >
> > śr., 4 wrz 2019 o 13:13 Piotr Zarzycki 
> > napisał(a):
> >
> >> I was able to produce ant artifacts on Mac! I will try get an RC1
> today.
> >>
> >> śr., 4 wrz 2019 o 11:11 Yishay Weiss 
> napisał(a):
> >>
> >>> Here’s what I’ve got.
> >>>
> >>>
> >>>
> >>> ANT_HOME
> >>>
> >>> C:\dev\ant\apache-ant-1.10.1
> >>>
> >>>
> >>>
> >>> 
> >>> From: Piotr Zarzycki 
> >>> Sent: Wednesday, September 4, 2019 11:56:02 AM
> >>> To: dev@royale.apache.org 
> >>> Subject: Re: Discuss of release steps preparation
> >>>
> >>> Hi Yishay,
> >>>
> >>> It was pretty stupid from my sight. I was certain that I have this
> env
> >>> variable setup, cause ant is working for me. I have no idea how.
> Let me
> >>> set
> >>> it and see whether it help.
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> śr., 4 wrz 2019 o 10:37 Yishay Weiss 
> >>> napisał(a):
> >>>
> >>> > >
> >>> >
> >>>
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
> >>> >
> >>>
> /Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
> >>> > does not exist.
> >>> >
> >>> >
> >>> >
> >>> > Is ANT_HOME env var defined?
> >>> >
> >>> >
> >>> >
> >>> > 
> >>> > From: Piotr Zarzycki 
> >>> > Sent: Wednesday, September 4, 2019 11:24:09 AM
> >>> > To: dev@royale.apache.org 
> >>> > Subject: Re: Discuss of release steps preparation
> >>> >
> >>> > Hi,
> >>> >
> >>> > It moved farther, but failed with different stacktrace [1]. I
> will try
> >>> to
> >>> > investigate this, unless someone has immediate idea why I got
> that
> >>> issue.
> >>> >
> >>> > [1]
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpaste.apache.org%2Fr48at&data=02%7C01%7Caharui%40adobe.com%7C4e25cee076954707866508d731511a64%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032096735701135&sdata=kqeCxKyMxz%2BZJuyDByWfU4Sp6mCRVIbr7bdK5GKFDr0%3D&reserved=0
> >>> >
> >>> > Thanks,
> >>> > Piotr
> >>> >
> >>> > śr., 4 wrz 2019 o 07:36 Alex Harui 
> >>> napisał(a):
> >>> >
> >>> > > FWIW, my Mac has:
> >>> > >
> >>> > > FLASHPLAYER_DEBUGGER='/Users//yyy/Flash Player
> >>> > > Debugger.app/Contents/MacOS/Flash Player Debugger'
> >>> > >
> >>> > > Note the single quotes instead of escaped spaces as described
> in the
> >>> > > README.  I think some code in Ant or the compiler doesn't
> handle
> >>> escaping
> >>> > > spaces correctly.
> >>> > >
> >>> > > The point of having someone else be the RM is to debug the

Re: Discuss of release steps preparation

[Alex Harui]

Piotr, 

Well, I can't tell you what to do, but if we want to encourage more frequent 
releases and more people volunteering to be the RM, at some point, somebody 
else besides me has to either create a rather complex step-by-step 
manual/runbook or help debug these scripts.  I'm willing to help with the 
latter, but I cannot without seeing the console output of prior steps.  This is 
a process or sequence.  The steps you run before matter to the step you are 
trying to run now.

-Alex

On 9/4/19, 9:19 AM, "Piotr Zarzycki"  wrote:

Hi Alex,

I know that is the goal, but I simply failed to meet those goals and I gave
up on that. I have artifacts and I would like to release Royale - that's
may goal, whether I do this in 90% automatically and 10% manually after so
many hours of work it doesn't matter to me now.

You are seeing full console output actually. Nothing more happen there.

Thanks,
Piotr

śr., 4 wrz 2019 o 18:11 Alex Harui  napisał(a):

> Again, the goal is here to debug the scripts, not to skip them.
>
> And it is hard to help without console output to examine.
>
> Yes, you have set the variables, but have the other steps run that
> generate an SVN working copy at that destination?  Show the console output
> related to it.
>
> HTH,
> -Alex
>
> On 9/4/19, 9:01 AM, "Piotr Zarzycki"  wrote:
>
> From that point I will probably upload artifacts manually and run RC1.
>
> śr., 4 wrz 2019 o 16:30 Piotr Zarzycki 
> napisał(a):
>
> > It looks like I have another problems. Target for uploading ant
> artifacts
> > is failing:
> >
> > ant -f releasesteps_asjs.xml Release_Step_013_Upload
> > -Drelease.version=0.9.6 -Drc=1
> >
> > Buildfile: /Users/piotr/Downloads/royale/releasesteps_asjs.xml
> >
> > check-name-and-svn:
> >  [echo] Name: 'Piotr Zarzycki'
> >  [echo] svn.dist.dev: /Users/piotr/Downloads/royale/dist/dev
> >  [echo] svn.dist.release:
> /Users/piotr/Downloads/royale/dist/release
> >  [echo] svn: /usr/bin/svn
> >
> > BUILD FAILED
> > /Users/piotr/Downloads/royale/releasesteps_asjs.xml:1537: The
> svn.dist.dev
> > property is not set to the working copy for
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev&data=02%7C01%7Caharui%40adobe.com%7C7a223df6f5d4435c17c008d731539953%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032107443413136&sdata=Et8HJHapB3FvMonYzhnsfNoonvUfRd1VNr5GUktMcDs%3D&reserved=0
> .
> >
> > As you can see above I have all properties setup cause I made an
> echo. I
> > don't understand what is happening...
> >
> > Thanks,
> > Piotr
> >
> > śr., 4 wrz 2019 o 13:13 Piotr Zarzycki 
> > napisał(a):
> >
> >> I was able to produce ant artifacts on Mac! I will try get an RC1
> today.
> >>
> >> śr., 4 wrz 2019 o 11:11 Yishay Weiss 
> napisał(a):
> >>
> >>> Here’s what I’ve got.
> >>>
> >>>
> >>>
> >>> ANT_HOME
> >>>
> >>> C:\dev\ant\apache-ant-1.10.1
> >>>
> >>>
> >>>
> >>> 
> >>> From: Piotr Zarzycki 
> >>> Sent: Wednesday, September 4, 2019 11:56:02 AM
> >>> To: dev@royale.apache.org 
> >>> Subject: Re: Discuss of release steps preparation
> >>>
> >>> Hi Yishay,
> >>>
> >>> It was pretty stupid from my sight. I was certain that I have this
> env
> >>> variable setup, cause ant is working for me. I have no idea how.
> Let me
> >>> set
> >>> it and see whether it help.
> >>>
> >>> Thanks,
> >>> Piotr
> >>>
> >>> śr., 4 wrz 2019 o 10:37 Yishay Weiss 
> >>> napisał(a):
> >>>
> >>> > >
> >>> >
> >>>
> 
/Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/build.xml:1636:
> >>> >
> >>>
> 
/Users/piotr/Downloads/royale/release/releaseasjs_ant/sources/royale-asjs/${env.ANT_HOME}/lib
> >>> > does not exist.
> >>> >
> >>> >
> >>> >
> >>> > Is ANT_HOME env var defined?
> >>> >
> >>> >
> >>> >
> >>> > 
> >>> > From: Piotr Zarzycki 
> >>> > Sent: Wednesday, September 4, 2019 11:24:09 AM
> >>> > To: dev@royale.apache.org 
> >>> > Subject: Re: Discuss of release steps preparation
> >>> >
> >>> > Hi,
> >>> >
> >>> > It moved farther, but failed with different stacktrace [1]. I
> will try
> >>> to
  

Re: Heads up on XML

[Greg Dove]

'Have you rummaged through the spec?'
Yes, if anything I probably need to step away from it and experience the
world a bit more! I have been focused on each portion of the spec as I
create unit tests and verify things between the player and the Royale
implementation.
I've also glanced a few times in the avmplus code, and that has provided
some clues where things were intentionally implemented slightly off spec,
but still a few things to figure out. However I am making progress - I
think I have everything covered for the codebase I am working on but I
will keep going beyond that. For that example above, I might be wrong, but
I suspect it is using a multiname with default namespace included for the
explicit call case in the player, but not for the implicit one, but I am
not yet sure why. I will double-check the spec though...


On Thu, Sep 5, 2019 at 4:02 AM Alex Harui  wrote:

> Don't know.  Have you rummaged through the spec?
>
> https://www.ecma-international.org/publications/files/ECMA-ST-WITHDRAWN/Ecma-357.pdf
>
> HTH,
> -Alex
>
> On 9/4/19, 3:11 AM, "Greg Dove"  wrote:
>
> This is particularly for Harbs and Yishay, as I think you are both (or
> both
> have been) using XML quite a bit. I have quite a few  fixes coming. All
> with tests that match on swf and js.
>
> I am currently working to demonstrate proof of concept to a prospective
> client for migration of a Flex app. The app makes extensive use of e4x
> and
> uses a bunch of features that I expect had not received attention
> previously, because they were originally either not working with the
> codebase I am porting, or i think some even caused errors in the
> javascript
> output.
>
> So I have spent the last several days almost full time figuring things
> out
> and working on fixes, between the compiler and emulation classes.
> All the previous XML tests continue to pass, but I have many more unit
> tests and fixes lined up for the following:
>
> namespace directives
> default xml namespace
> use namespace (multiple)
>
> a number of fixes for xml filtering, including:
> -'this' resolves correctly in filters that include external references
> from
> the fitler expression to the 'this' scope
> -handles alternate ordering of comparisons between XML 'getters' and
> literals
> e.g. something.(name() = "cat")  or something.("cat" = name()) (these
> are
> the same)
> -it (will) now handle XML e4x references in nested function calls
> inside
> the filter, e.g. things like:
> e.g.
> var people:XML = 
> 
> Bob
> 32
> 
> 
> Joe
> 46
> 
> ;
>  var findJoeByAge:Function = function (i:int):Boolean {
> return i > 40;
> };
> people.person.(findJoeByAge(parseInt(age))).name
>
>
> I have lots more granular tests in QName, Namespace, and XML with
> tuning to
> improve reliability.
> toXMLString XML node output also matches flash more correctly in what I
> have coming.
>
> One thing that I am trying to figure out, which I would appreciate
> input on
> if someone has an answer:
> For the example:
>
> var feed:XML = new XML(
> 'https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C4fc6b31478da4718992c08d7312038b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031886769375971&sdata=YxDoQRD0NhfUfCK1QWIazLqeiP7vNRFFCaOLFF1NIow%3D&reserved=0
> "
> xmlns:m="nothing">\n' +
> '   href="blah/12321/domain/"/>\n' +
> '\n');
> var atomSpace:Namespace = new Namespace('
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C4fc6b31478da4718992c08d7312038b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031886769375971&sdata=YxDoQRD0NhfUfCK1QWIazLqeiP7vNRFFCaOLFF1NIow%3D&reserved=0'
> );
>
> Can anyone explain why this (in SWF, as a reference implementation):
> trace(feed.atomSpace::link.length())
> trace(feed.atomSpace::link.toXMLString())
> //output:
> 0
> {empty string}
> is different to:
> trace(feed.child(new QName(atomSpace,'link')).length())
> trace(feed.child(new QName(atomSpace,'link')).toXMLString())
> //output:
> 1
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C4fc6b31478da4718992c08d7312038b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637031886769375971&sdata=YxDoQRD0NhfUfCK1QWIazLqeiP7vNRFFCaOLFF1NIow%3D&reserved=0";
> xmlns:m="nothing"/>
>
> I had assumed the above cases would be the same, but the second one is
> behaving as if it

Re: Heads up on XML

[Alex Harui]

Speaking of multinames, what is the ABC code generated by the Flex compiler for 
the two cases?  It might contain some clues.  I would have expected both to 
return "1" and the node.  But I did see in the spec the notion of 
"InScopeNamespaces".  I generally hate reading specs like these so I am not 
very knowledgeable about what the spec says.

HTH,
-Alex

On 9/4/19, 11:05 AM, "Greg Dove"  wrote:

'Have you rummaged through the spec?'
Yes, if anything I probably need to step away from it and experience the
world a bit more! I have been focused on each portion of the spec as I
create unit tests and verify things between the player and the Royale
implementation.
I've also glanced a few times in the avmplus code, and that has provided
some clues where things were intentionally implemented slightly off spec,
but still a few things to figure out. However I am making progress - I
think I have everything covered for the codebase I am working on but I
will keep going beyond that. For that example above, I might be wrong, but
I suspect it is using a multiname with default namespace included for the
explicit call case in the player, but not for the implicit one, but I am
not yet sure why. I will double-check the spec though...


On Thu, Sep 5, 2019 at 4:02 AM Alex Harui  wrote:

> Don't know.  Have you rummaged through the spec?
>
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ecma-international.org%2Fpublications%2Ffiles%2FECMA-ST-WITHDRAWN%2FEcma-357.pdf&data=02%7C01%7Caharui%40adobe.com%7C8b56d09a6a314e2d55aa08d731628822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637032171567244570&sdata=8LW6weJevEYXpCx%2FEdegixnO%2BgVXDasn3gjKZFOrPFI%3D&reserved=0
>
> HTH,
> -Alex
>
> On 9/4/19, 3:11 AM, "Greg Dove"  wrote:
>
> This is particularly for Harbs and Yishay, as I think you are both (or
> both
> have been) using XML quite a bit. I have quite a few  fixes coming. 
All
> with tests that match on swf and js.
>
> I am currently working to demonstrate proof of concept to a 
prospective
> client for migration of a Flex app. The app makes extensive use of e4x
> and
> uses a bunch of features that I expect had not received attention
> previously, because they were originally either not working with the
> codebase I am porting, or i think some even caused errors in the
> javascript
> output.
>
> So I have spent the last several days almost full time figuring things
> out
> and working on fixes, between the compiler and emulation classes.
> All the previous XML tests continue to pass, but I have many more unit
> tests and fixes lined up for the following:
>
> namespace directives
> default xml namespace
> use namespace (multiple)
>
> a number of fixes for xml filtering, including:
> -'this' resolves correctly in filters that include external references
> from
> the fitler expression to the 'this' scope
> -handles alternate ordering of comparisons between XML 'getters' and
> literals
> e.g. something.(name() = "cat")  or something.("cat" = name()) (these
> are
> the same)
> -it (will) now handle XML e4x references in nested function calls
> inside
> the filter, e.g. things like:
> e.g.
> var people:XML = 
> 
> Bob
> 32
> 
> 
> Joe
> 46
> 
> ;
>  var findJoeByAge:Function = function (i:int):Boolean {
> return i > 40;
> };
> people.person.(findJoeByAge(parseInt(age))).name
>
>
> I have lots more granular tests in QName, Namespace, and XML with
> tuning to
> improve reliability.
> toXMLString XML node output also matches flash more correctly in what 
I
> have coming.
>
> One thing that I am trying to figure out, which I would appreciate
> input on
> if someone has an answer:
> For the example:
>
> var feed:XML = new XML(
> 'https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.w3.org%2F2005%2FAtom&data=02%7C01%7Caharui%40adobe.com%7C8b56d09a6a314e2d55aa08d731628822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637032171567244570&sdata=MGdQ%2FHKuHFqdLQtVw2I%2FO4OWBI5sjyDH7PxEu9Ezmh4%3D&reserved=0
> "
> xmlns:m="nothing">\n' +
> '   href="blah/12321/domain/"/>\n' +
> '\n');
> var atomSpace:Namespace = new Namespace('
> 
https://nam04.safelinks.protect

Re: Heads up on XML

[Greg Dove]

Good idea. I'll check the swf output, although probably tomorrow as I need
to focus on something else today.
' I would have expected both to return "1" and the node.  '

In that example I would expect the opposite (because the the link node
being returned by the second query is not in the specified explicit
namespace of the QName), so I am curious to understand why you think
that... maybe it will help me understand.

When I use feed.atom::link I expect only links that are bound to the atom
namespace (uri). Because  node has no prefix bound to the uri
that the atom namespace defines, and it is in the default namespace, I
would not expect it to be included.
At the moment the atom::link part is working the same as swf, so I'm happy
with that at least for what I am working on. All the explicit calls to
child(name) or descendants(name) in the app I am working on use string args
so these all work correctly as well.
I'm just trying to cover things for the future... while my head is still in
this stuff.



On Thu, Sep 5, 2019 at 6:11 AM Alex Harui  wrote:

> Speaking of multinames, what is the ABC code generated by the Flex
> compiler for the two cases?  It might contain some clues.  I would have
> expected both to return "1" and the node.  But I did see in the spec the
> notion of "InScopeNamespaces".  I generally hate reading specs like these
> so I am not very knowledgeable about what the spec says.
>
> HTH,
> -Alex
>
> On 9/4/19, 11:05 AM, "Greg Dove"  wrote:
>
> 'Have you rummaged through the spec?'
> Yes, if anything I probably need to step away from it and experience
> the
> world a bit more! I have been focused on each portion of the spec as I
> create unit tests and verify things between the player and the Royale
> implementation.
> I've also glanced a few times in the avmplus code, and that has
> provided
> some clues where things were intentionally implemented slightly off
> spec,
> but still a few things to figure out. However I am making progress - I
> think I have everything covered for the codebase I am working on
> but I
> will keep going beyond that. For that example above, I might be wrong,
> but
> I suspect it is using a multiname with default namespace included for
> the
> explicit call case in the player, but not for the implicit one, but I
> am
> not yet sure why. I will double-check the spec though...
>
>
> On Thu, Sep 5, 2019 at 4:02 AM Alex Harui 
> wrote:
>
> > Don't know.  Have you rummaged through the spec?
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ecma-international.org%2Fpublications%2Ffiles%2FECMA-ST-WITHDRAWN%2FEcma-357.pdf&data=02%7C01%7Caharui%40adobe.com%7C8b56d09a6a314e2d55aa08d731628822%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637032171567244570&sdata=8LW6weJevEYXpCx%2FEdegixnO%2BgVXDasn3gjKZFOrPFI%3D&reserved=0
> >
> > HTH,
> > -Alex
> >
> > On 9/4/19, 3:11 AM, "Greg Dove"  wrote:
> >
> > This is particularly for Harbs and Yishay, as I think you are
> both (or
> > both
> > have been) using XML quite a bit. I have quite a few  fixes
> coming. All
> > with tests that match on swf and js.
> >
> > I am currently working to demonstrate proof of concept to a
> prospective
> > client for migration of a Flex app. The app makes extensive use
> of e4x
> > and
> > uses a bunch of features that I expect had not received attention
> > previously, because they were originally either not working with
> the
> > codebase I am porting, or i think some even caused errors in the
> > javascript
> > output.
> >
> > So I have spent the last several days almost full time figuring
> things
> > out
> > and working on fixes, between the compiler and emulation classes.
> > All the previous XML tests continue to pass, but I have many
> more unit
> > tests and fixes lined up for the following:
> >
> > namespace directives
> > default xml namespace
> > use namespace (multiple)
> >
> > a number of fixes for xml filtering, including:
> > -'this' resolves correctly in filters that include external
> references
> > from
> > the fitler expression to the 'this' scope
> > -handles alternate ordering of comparisons between XML 'getters'
> and
> > literals
> > e.g. something.(name() = "cat")  or something.("cat" = name())
> (these
> > are
> > the same)
> > -it (will) now handle XML e4x references in nested function calls
> > inside
> > the filter, e.g. things like:
> > e.g.
> > var people:XML = 
> > 
> > Bob
> > 32
> > 
> > 
> > Joe
> > 46
>   

Re: Heads up on XML

[Harbs]

Heads up:

I did some (on first blush) odd things in XML related to QNames. QNames are 
pooled and many XML properties are not initialized by default. The reason I did 
this was it avoided many MB of memory waste for complex XML. Please don’t mess 
that up.

Thanks,
Harbs

> On Sep 4, 2019, at 1:02 PM, Greg Dove  wrote:
> 
> This is particularly for Harbs and Yishay, as I think you are both (or both
> have been) using XML quite a bit. I have quite a few  fixes coming. All
> with tests that match on swf and js.
> 
> I am currently working to demonstrate proof of concept to a prospective
> client for migration of a Flex app. The app makes extensive use of e4x and
> uses a bunch of features that I expect had not received attention
> previously, because they were originally either not working with the
> codebase I am porting, or i think some even caused errors in the javascript
> output.
> 
> So I have spent the last several days almost full time figuring things out
> and working on fixes, between the compiler and emulation classes.
> All the previous XML tests continue to pass, but I have many more unit
> tests and fixes lined up for the following:
> 
> namespace directives
> default xml namespace
> use namespace (multiple)
> 
> a number of fixes for xml filtering, including:
> -'this' resolves correctly in filters that include external references from
> the fitler expression to the 'this' scope
> -handles alternate ordering of comparisons between XML 'getters' and
> literals
> e.g. something.(name() = "cat")  or something.("cat" = name()) (these are
> the same)
> -it (will) now handle XML e4x references in nested function calls inside
> the filter, e.g. things like:
> e.g.
> var people:XML = 
>
>Bob
>32
>
>
>Joe
>46
>
>;
> var findJoeByAge:Function = function (i:int):Boolean {
>return i > 40;
>};
> people.person.(findJoeByAge(parseInt(age))).name
> 
> 
> I have lots more granular tests in QName, Namespace, and XML with tuning to
> improve reliability.
> toXMLString XML node output also matches flash more correctly in what I
> have coming.
> 
> One thing that I am trying to figure out, which I would appreciate input on
> if someone has an answer:
> For the example:
> 
> var feed:XML = new XML(
>'http://www.w3.org/2005/Atom";
> xmlns:m="nothing">\n' +
>'   href="blah/12321/domain/"/>\n' +
>'\n');
> var atomSpace:Namespace = new Namespace('http://www.w3.org/2005/Atom');
> 
> Can anyone explain why this (in SWF, as a reference implementation):
> trace(feed.atomSpace::link.length())
> trace(feed.atomSpace::link.toXMLString())
> //output:
> 0
> {empty string}
> is different to:
> trace(feed.child(new QName(atomSpace,'link')).length())
> trace(feed.child(new QName(atomSpace,'link')).toXMLString())
> //output:
> 1
> http://www.w3.org/2005/Atom"; xmlns:m="nothing"/>
> 
> I had assumed the above cases would be the same, but the second one is
> behaving as if it has the default namespace included with the specified
> namespace in the QName matching (it does correctly match the namespace
> specifically as well -with e.g.  bound to the uri, but also seems to include link nodes with the default
> namespace, whether or not it is declared). I can accommodate this
> difference to make them behave the same, I just would like to understand
> the basis for the actual rules if anyone knows
> 
> I should be in a position to push the updates this coming weekend I think.

Re: Heads up on XML

[Greg Dove]

Yeah, I saw that ;) Don't worry, I am aware of it.

My first goal is to make sure it works like it should, because that comes
first, and then to optimize. I'll check the memory side of things and make
sure it's at least the same as before. If you can point me to some
publicly accessible large test cases that would be really helpful. I will
work through that before I push anything.

On Thu, Sep 5, 2019 at 7:26 AM Harbs  wrote:

> Heads up:
>
> I did some (on first blush) odd things in XML related to QNames. QNames
> are pooled and many XML properties are not initialized by default. The
> reason I did this was it avoided many MB of memory waste for complex XML.
> Please don’t mess that up.
>
> Thanks,
> Harbs
>
> > On Sep 4, 2019, at 1:02 PM, Greg Dove  wrote:
> >
> > This is particularly for Harbs and Yishay, as I think you are both (or
> both
> > have been) using XML quite a bit. I have quite a few  fixes coming. All
> > with tests that match on swf and js.
> >
> > I am currently working to demonstrate proof of concept to a prospective
> > client for migration of a Flex app. The app makes extensive use of e4x
> and
> > uses a bunch of features that I expect had not received attention
> > previously, because they were originally either not working with the
> > codebase I am porting, or i think some even caused errors in the
> javascript
> > output.
> >
> > So I have spent the last several days almost full time figuring things
> out
> > and working on fixes, between the compiler and emulation classes.
> > All the previous XML tests continue to pass, but I have many more unit
> > tests and fixes lined up for the following:
> >
> > namespace directives
> > default xml namespace
> > use namespace (multiple)
> >
> > a number of fixes for xml filtering, including:
> > -'this' resolves correctly in filters that include external references
> from
> > the fitler expression to the 'this' scope
> > -handles alternate ordering of comparisons between XML 'getters' and
> > literals
> > e.g. something.(name() = "cat")  or something.("cat" = name()) (these are
> > the same)
> > -it (will) now handle XML e4x references in nested function calls inside
> > the filter, e.g. things like:
> > e.g.
> > var people:XML = 
> >
> >Bob
> >32
> >
> >
> >Joe
> >46
> >
> >;
> > var findJoeByAge:Function = function (i:int):Boolean {
> >return i > 40;
> >};
> > people.person.(findJoeByAge(parseInt(age))).name
> >
> >
> > I have lots more granular tests in QName, Namespace, and XML with tuning
> to
> > improve reliability.
> > toXMLString XML node output also matches flash more correctly in what I
> > have coming.
> >
> > One thing that I am trying to figure out, which I would appreciate input
> on
> > if someone has an answer:
> > For the example:
> >
> > var feed:XML = new XML(
> >'http://www.w3.org/2005/Atom";
> > xmlns:m="nothing">\n' +
> >'   > href="blah/12321/domain/"/>\n' +
> >'\n');
> > var atomSpace:Namespace = new Namespace('http://www.w3.org/2005/Atom');
> >
> > Can anyone explain why this (in SWF, as a reference implementation):
> > trace(feed.atomSpace::link.length())
> > trace(feed.atomSpace::link.toXMLString())
> > //output:
> > 0
> > {empty string}
> > is different to:
> > trace(feed.child(new QName(atomSpace,'link')).length())
> > trace(feed.child(new QName(atomSpace,'link')).toXMLString())
> > //output:
> > 1
> > http://www.w3.org/2005/Atom"; xmlns:m="nothing"/>
> >
> > I had assumed the above cases would be the same, but the second one is
> > behaving as if it has the default namespace included with the specified
> > namespace in the QName matching (it does correctly match the namespace
> > specifically as well -with e.g.  > bound to the uri, but also seems to include link nodes with the default
> > namespace, whether or not it is declared). I can accommodate this
> > difference to make them behave the same, I just would like to understand
> > the basis for the actual rules if anyone knows
> >
> > I should be in a position to push the updates this coming weekend I
> think.
>
>

Re: Heads up on XML

[Alex Harui]

I read the example incorrectly.  So yeah, it should return 0 and empty string 
in both cases, IMO.  There might be some subtlety in how the namespaces are 
specified for a QName or how QName works in child().

HTH,
-Alex

On 9/4/19, 11:33 AM, "Greg Dove"  wrote:

Good idea. I'll check the swf output, although probably tomorrow as I need
to focus on something else today.
' I would have expected both to return "1" and the node.  '

In that example I would expect the opposite (because the the link node
being returned by the second query is not in the specified explicit
namespace of the QName), so I am curious to understand why you think
that... maybe it will help me understand.

When I use feed.atom::link I expect only links that are bound to the atom
namespace (uri). Because  node has no prefix bound to the uri
that the atom namespace defines, and it is in the default namespace, I
would not expect it to be included.
At the moment the atom::link part is working the same as swf, so I'm happy
with that at least for what I am working on. All the explicit calls to
child(name) or descendants(name) in the app I am working on use string args
so these all work correctly as well.
I'm just trying to cover things for the future... while my head is still in
this stuff.



On Thu, Sep 5, 2019 at 6:11 AM Alex Harui  wrote:

> Speaking of multinames, what is the ABC code generated by the Flex
> compiler for the two cases?  It might contain some clues.  I would have
> expected both to return "1" and the node.  But I did see in the spec the
> notion of "InScopeNamespaces".  I generally hate reading specs like these
> so I am not very knowledgeable about what the spec says.
>
> HTH,
> -Alex
>
> On 9/4/19, 11:05 AM, "Greg Dove"  wrote:
>
> 'Have you rummaged through the spec?'
> Yes, if anything I probably need to step away from it and experience
> the
> world a bit more! I have been focused on each portion of the spec as I
> create unit tests and verify things between the player and the Royale
> implementation.
> I've also glanced a few times in the avmplus code, and that has
> provided
> some clues where things were intentionally implemented slightly off
> spec,
> but still a few things to figure out. However I am making progress - I
> think I have everything covered for the codebase I am working on
> but I
> will keep going beyond that. For that example above, I might be wrong,
> but
> I suspect it is using a multiname with default namespace included for
> the
> explicit call case in the player, but not for the implicit one, but I
> am
> not yet sure why. I will double-check the spec though...
>
>
> On Thu, Sep 5, 2019 at 4:02 AM Alex Harui 
> wrote:
>
> > Don't know.  Have you rummaged through the spec?
> >
> >
> 
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ecma-international.org%2Fpublications%2Ffiles%2FECMA-ST-WITHDRAWN%2FEcma-357.pdf&data=02%7C01%7Caharui%40adobe.com%7C1ade69b1ed4844c4371f08d731665509%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637032187917207574&sdata=gFsLnUcRjOioiOWViLttSkIBsISlcN%2F9AlGhpC4rX1c%3D&reserved=0
> >
> > HTH,
> > -Alex
> >
> > On 9/4/19, 3:11 AM, "Greg Dove"  wrote:
> >
> > This is particularly for Harbs and Yishay, as I think you are
> both (or
> > both
> > have been) using XML quite a bit. I have quite a few  fixes
> coming. All
> > with tests that match on swf and js.
> >
> > I am currently working to demonstrate proof of concept to a
> prospective
> > client for migration of a Flex app. The app makes extensive use
> of e4x
> > and
> > uses a bunch of features that I expect had not received 
attention
> > previously, because they were originally either not working with
> the
> > codebase I am porting, or i think some even caused errors in the
> > javascript
> > output.
> >
> > So I have spent the last several days almost full time figuring
> things
> > out
> > and working on fixes, between the compiler and emulation 
classes.
> > All the previous XML tests continue to pass, but I have many
> more unit
> > tests and fixes lined up for the following:
> >
> > namespace directives
> > default xml namespace
> > use namespace (multiple)
> >
> > a number of fixes for xml filtering, including:
> > -'this' resolves correctly in filters that include external
> references
> > from
> 

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

[Apache Royale CI Server]

See 

Build failed in Jenkins: royale-asjs_MXTests #1121

[Apache Royale CI Server]

See 


--
[...truncated 967.68 KB...]
[mxmlc] scanning for overrides: SolidBorderUtil
[mxmlc] scanning for overrides: StringTrimmer
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: Timer
[mxmlc] scanning for overrides: UIUtils
[mxmlc] scanning for overrides: Effect
[mxmlc] scanning for overrides: Transition
[mxmlc] scanning for overrides: IFill
[mxmlc] scanning for overrides: SolidColor
[mxmlc] scanning for overrides: IExternalizable
[mxmlc] scanning for overrides: Proxy
[mxmlc] scanning for overrides: CursorBookmark
[mxmlc] scanning for overrides: ICollectionView
[mxmlc] scanning for overrides: IList
[mxmlc] scanning for overrides: IViewCursor
[mxmlc] scanning for overrides: ListCollectionView
[mxmlc] scanning for overrides: ListCollectionViewCursor
[mxmlc] scanning for overrides: ListCollectionViewBookmark
[mxmlc] scanning for overrides: ArrayCollection
[mxmlc] scanning for overrides: ArrayList
[mxmlc] scanning for overrides: XMLListCollection
[mxmlc] scanning for overrides: CanvasLayout
[mxmlc] scanning for overrides: Flex
[mxmlc] scanning for overrides: BoxDirection
[mxmlc] scanning for overrides: HBox
[mxmlc] scanning for overrides: PanelTitleBar
[mxmlc] scanning for overrides: DataGridColumn
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ISelectable
[mxmlc] scanning for overrides: CheckBox
[mxmlc] scanning for overrides: IFocusManagerComponent
[mxmlc] scanning for overrides: ComboBase
[mxmlc] scanning for overrides: ComboBox
[mxmlc] scanning for overrides: ScrollControlBase
[mxmlc] scanning for overrides: ListBase
[mxmlc] scanning for overrides: DataGrid
[mxmlc] scanning for overrides: DateField
[mxmlc] scanning for overrides: Label
[mxmlc] scanning for overrides: List
[mxmlc] scanning for overrides: MenuBar
[mxmlc] scanning for overrides: NumericStepper
[mxmlc] scanning for overrides: RadioButton
[mxmlc] scanning for overrides: RadioButtonGroup
[mxmlc] scanning for overrides: TextArea
[mxmlc] scanning for overrides: ITextInput
[mxmlc] scanning for overrides: TextInput
[mxmlc] scanning for overrides: ITextFieldFactory
[mxmlc] scanning for overrides: Singleton
[mxmlc] scanning for overrides: ItemClickEvent
[mxmlc] scanning for overrides: ListEvent
[mxmlc] scanning for overrides: MenuEvent
[mxmlc] scanning for overrides: MouseEvent
[mxmlc] scanning for overrides: PropertyChangeEventKind
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: Matrix
[mxmlc] scanning for overrides: IFocusManagerComplexComponent
[mxmlc] scanning for overrides: IFocusManagerGroup
[mxmlc] scanning for overrides: IResourceBundle
[mxmlc] scanning for overrides: ResourceManagerImpl
[mxmlc] scanning for overrides: ResourceModuleInfo
[mxmlc] scanning for overrides: ResourceEventDispatcher
[mxmlc] scanning for overrides: ResourceBundleProxy
[mxmlc] scanning for overrides: GroupBase
[mxmlc] scanning for overrides: SkinnableComponent
[mxmlc] scanning for overrides: ButtonBase
[mxmlc] scanning for overrides: Button
[mxmlc] scanning for overrides: ErrorArray
[mxmlc] scanning for overrides: RunCodeEvent
[mxmlc] scanning for overrides: PasswordInputBead
[mxmlc] scanning for overrides: ITileLayout
[mxmlc] scanning for overrides: TileLayout
[mxmlc] scanning for overrides: LocaleUtils
[mxmlc] scanning for overrides: StringPadder
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: IStroke
[mxmlc] scanning for overrides: CursorError
[mxmlc] scanning for overrides: SortError
[mxmlc] scanning for overrides: ISort
[mxmlc] scanning for overrides: Sort
[mxmlc] scanning for overrides: IXMLNotifiable
[mxmlc] scanning for overrides: XMLListAdapter
[mxmlc] scanning for overrides: FlexChildInfo
[mxmlc] scanning for overrides: BaseListData
[mxmlc] scanning for overrides: IFactory
[mxmlc] scanning for overrides: IUITextField
[mxmlc] scanning for overrides: UITextField
[mxmlc] scanning for overrides: CollectionEvent
[mxmlc] scanning for overrides: CollectionEventKind
[mxmlc] scanning for overrides: LocaleSorter
[mxmlc] scanning for overrides: LocaleID
[mxmlc] scanning for overrides: LocaleRegistry
[mxmlc] scanning for overrides: ResourceBundle
[mxmlc] scanning for overrides: ArrayUtil
[mxmlc] scanning for overrides: StringUtil
[mxmlc] scanning for overrides: UIDUtil
[mxmlc] scanning for overrides: DataGroup
[mxmlc] scanning for overrides: LayoutBase
[mxmlc] scanning for overrides: BasicLayout
[mxmlc] scanning for overrides: IBinaryDataInput