You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by "Justin M. Hill" <Ju...@Prominic.NET> on 2019/04/27 04:52:04 UTC
Let's bump Royale version to 1.0 -- submit your bid for assistance to the
group by Friday May 3
Hi Dany,
Are you willing to write an article about why users should choose or at
least consider heavily Apache Royale over the competitors - React, Vue, and
Angular?
I think it is important to clearly explain "Why you should care about
Royale" on the homepage compared to the competitors you mentioned.
Ideally, this article would be written not just for those with an
ActionScript or Flex code base that are seeking a modernization target.
The Moonshine IDE team is willing to donate $2,500 USD in total over the
next 30 days to anyone who can accomplish what Alex and Carlos want to see
happen to call it release 1.0.
IF you who are willing to step up to the plate immediately (with a
deliverable no later than May 26, 2019) to help with:
* documentation (ASDoc style)
* examples (code snippets that do things like Tour de Royale)
* tutorials (well written, friendly, understandable, educational material)
* a mini reproduction of the aforementioned Flex In a Week Series (great
idea!)
https://www.adobe.com/devnet/flex/videotraining.html
* build automation
* automated test cases
* creation of a summary comparison table showing Royale relative to React,
Vue, Angular
* a longer write up of competitive articles detailed why Royale is
important. BTW, one reason it can be important is because it is NOT
controlled by giant companies.
* a directory of consultants for hire:
* OR anything else Alex and Carlos specifically need to be convinced to
push to 1.0 release
THEN
Please submit to this public group your commitment and cost.
We will then do this democratically:
deadline for bid submissions is 7 days from now -- Friday May 3.
Carlos (or someone who knows Twitter enough to create another poll) will
then do another Twitter vote poll for 3 days to decide who gets the bids
Ideally multiple people will commit to doing something "small" for $500
each and we can award 5 people the projects.
The $2,500 USD total will be paid via PayPal. No exceptions.
IF within 30 days Apache Royale 1.0 is released to the public then the
Moonshine IDE team will again donate $2,500 for the month of June in an
identical voting scenario (assuming this one works well) to bring home a
1.1 release.
By 60 days from now, a new user who has never seen Royale before or
programmed in ActionScript should be able to:
1) Arrive at the Apache Royale web page
2) Understand from the home page why they should care about the project if
they come from React, Vue, Angular, Flex, or ActionScript worlds
3) Be able to within 5 mouse clicks (download button, install button,
launch button, build button, run button) go from having nothing on their
machine to having an IDE (we of course volunteer Moonshine but Visual
Studio Code should be a goal for this, too) on their machine with a
successful build of their first "hello world". No command line nonsense.
No learning NPM, Git, downloading 20 required packages. See Royale
website. Want to try it. 5 clicks later build your Hello World.
If the above 3 goals are met, then the Moonshine IDE team will run a 3rd
donation round of $2,500 for the month of July in a manner to the
description above to bring home a 1.2 release, to be published no later
than the end of July 2019 for the awards to be paid.
Hopefully this helps motivate the team.
Thank you,
Justin Hill
From: dev-digest-help@royale.apache.org
To: dev@royale.apache.org
Date: 04/26/2019 11:04 PM
Subject: [External] dev Digest 27 Apr 2019 04:04:13 -0000 Issue 1966 -
Dany replies about React, Vue, Angular
dev Digest 27 Apr 2019 04:04:13 -0000 Issue 1966
Topics (messages 9894 through 9902)
Re: Let's bump Royale version to 1.0
9894 by: Dany Dhondt
9896 by: Carlos Rovira
Re: Version property (was: Let's bump Royale version to 1.0)
9895 by: Alex Harui
Release Step 001 Succeeded
9897 by: Apache Royale CI Server
Release Step 001a Succeeded
9898 by: Apache Royale CI Server
Release Step 002 Succeeded
9899 by: Apache Royale CI Server
Release Step 002a Succeeded
9900 by: Apache Royale CI Server
Release Step 003 Succeeded
9901 by: Apache Royale CI Server
Build failed in Jenkins: royale-asjs_MXTests #722
9902 by: Apache Royale CI Server
Administrivia:
---------------------------------------------------------------------
To post to the list, e-mail: dev@royale.apache.org
To unsubscribe, e-mail: dev-digest-unsubscribe@royale.apache.org
For additional commands, e-mail: dev-digest-help@royale.apache.org
----------------------------------------------------------------------
----- Message from Dany Dhondt <ar...@mac.com.INVALID> on Fri, 26 Apr
2019 16:06:59 +0200 -----
To: dev@royale.apache.org
Subject: Re: Let's bump Royale
version to 1.0
I’m all for buikding a knowledge base in Stack Overflow! The mailing list
should only be used for developing Royale. Questions about using Royale
should go to SO
The competitors of Royale are React, Vue, Angular, ...
Lots of developers are now used to those workflows.
In case of React, create-react-app sets you up with a brand new, ready to
go project in less than 30 seconds. That should be a benchmark for Royale
imo.
Dany
Verstuurd vanaf mijn iPhone
> Op 26 apr. 2019 om 12:42 heeft Frost, Andrew <An...@harman.com>
het volgende geschreven:
>
> One other thought ... currently the way people ask for support is via
these mailing lists. Which are okay but I'm always conscious that I'm
potentially spamming people, plus the volume of mails is such that I have a
rule to push all these into a folder that I then review every day or two..
>
> But if I want to find something out, I tend not to go search the mailing
list, I tend to search online. Looking through mailing list threads isn't
the easiest (and search engines don't necessarily pick things up from them
very well) but a major source of support is Stack Overflow... I use this a
lot with my other work and there's a lot of information there.
>
> Apache Royale doesn't appear to have a tag; when I search for "royale"
all I got was stuff about "Clash Royale"; there are however 8 questions
with "flexjs" tags.
>
> But wouldn't it be good for people to add questions and to contribute
answers there, both from the user perspective and perhaps also the dev
perspective? Would be interested in people's thoughts... (and perhaps I'll
have to dig out my SO credentials to start contributing there....)
>
> thanks
>
> Andrew
>
>
> -----Original Message-----
> From: Carlos Rovira [mailto:carlosrovira@apache.org]
> Sent: 26 April 2019 10:39
> To: dev@royale.apache.org
> Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0
>
> Hi Angelo, that's great! :)
>
> any help here is very appreciated.
>
> Share in a new mail a concrete contribution before starting to work on
it, so we can know about it and help you on the task so your work fit
perfectly in the overall picture.
>
> I'd like to create videos too, and people asked about it in facebook and
twitter. Do you have skills in creating videos?
>
>
>
> El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari
(<la...@gmail.com>)
> escribió:
>
>> Yes, i can give some slots to help with documentation or example
>> project or so... I think tutorial videos could be help to understand
>> rapidly the platform and could help new user to get ready in a few
>> hours to start build their project.
>>
>> Angelo
>>
>> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira
>> <ca...@apache.org>
>> wrote:
>>
>>> Agree with latest comments.
>>>
>>> I think we should work in docs and ease the start of new users to
>>> target
>>> 1.0
>>> And in the process fix some few things (i.e: don't want to reach 1.0
>>> with Jewel Table in its current state and API)
>>>
>>> What do you think?
>>>
>>> If you all agree could you think on how to contribute to that
>>> effort? Can we have as a near goal to bring 1.0 planing ourselves to
>>> donate some
>> hours
>>> to Apache Royale to make this happen? If some of us help in the
>>> current state I think we can get to it sooner.
>>>
>>> Thanks
>>>
>>>
>>> El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
>>> lazzari.angelo@gmail.com>)
>>> escribió:
>>>
>>>> I am completely agree with Olaf: start using a new platform where
>>>> the documentation is not complete, clean and updated it is a
>>>> really bad thing...and it would be a potential reason to increase
>>>> the difficulty
>> to
>>>> adopt the platform...
>>>>
>>>> Angelo
>>>>
>>>> El vie., 26 abr. 2019 8:54, Olaf Krueger <ma...@olafkrueger.net>
>>> escribió:
>>>>
>>>>> Hi,
>>>>>
>>>>> Basically, I think it's important to provide a great developer
>>>> experience.
>>>>> IMO, that's more important than trying to implement missing features.
>>>>>
>>>>> One thing to achieve this is documentation of course.
>>>>> Thanks to all of you there already exist a lot of docs, but it
>>>>> feels
>> a
>>>> bit
>>>>> messy because they are hosted at different places, e.g.:
>>>>>
>>>>> - royale-docs repo
>>>>> - royale-asjs wiki
>>>>> - royale-asjs Readme
>>>>> -
>>>>> https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http
>>>>> s%3A%2F%2Froyale.apache.org
>>>>> - ...?
>>>>>
>>>>> As a user, it's hard to get an overview of what is available...
>>>>> and
>>>> where.
>>>>> Maybe it's a good idea to consolidate the docs before releasing 1.0.
>>>>>
>>>>> Just my 2 cents,
>>>>> Olaf
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Sent from:
>>>>> https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http
>>>>> %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
>>>>>
>>>>
>>>
>>>
>>> --
>>> Carlos Rovira
>>> https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%
>>> 2F%2Fabout.me%2Fcarlosrovira
>>>
>>
>>
>> --
>> Angelo Lazzari
>> mobile: +34 683 137 087
>> mail: lazzari.angelo@gmail.com
>>
>>
>>
>> ----------------------------------------------------------------------
>> --------------------------------------------------
>> Verify the correspondence of the addressee; otherwise, notify that to
>> the sender and, conscious of the responsibility for the undue use,
>> destroy the message and its copies.
>>
>> ----------------------------------------------------------------------
>> --------------------------------------------------
>>
>
>
> --
> Carlos Rovira
>
https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira
----- Message from Carlos Rovira <ca...@apache.org> on Fri, 26 Apr
2019 20:45:32 +0200 -----
To: dev@royale.apache.org
Subject: Re: Let's bump Royale
version to 1.0
That's great Angelo! :)
El vie., 26 abr. 2019 a las 13:06, Angelo Lazzari
(<la...@gmail.com>)
escribió:
> yes, I always send video to my client, it is a really good way to explain
> new process and teach things...
>
> I will write a new email about the video course...
>
> Angelo
>
> On Fri, Apr 26, 2019 at 11:39 AM Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Hi Angelo, that's great! :)
> >
> > any help here is very appreciated.
> >
> > Share in a new mail a concrete contribution before starting to work on
> it,
> > so we can know about it and help you on the task so your work fit
> perfectly
> > in the overall picture.
> >
> > I'd like to create videos too, and people asked about it in facebook
and
> > twitter. Do you have skills in creating videos?
> >
> >
> >
> > El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<
> > lazzari.angelo@gmail.com>)
> > escribió:
> >
> > > Yes, i can give some slots to help with documentation or example
> project
> > or
> > > so... I think tutorial videos could be help to understand rapidly the
> > > platform and could help new user to get ready in a few hours to start
> > build
> > > their project.
> > >
> > > Angelo
> > >
> > > On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira <
> carlosrovira@apache.org>
> > > wrote:
> > >
> > > > Agree with latest comments.
> > > >
> > > > I think we should work in docs and ease the start of new users to
> > target
> > > > 1.0
> > > > And in the process fix some few things (i.e: don't want to reach
1.0
> > with
> > > > Jewel Table in its current state and API)
> > > >
> > > > What do you think?
> > > >
> > > > If you all agree could you think on how to contribute to that
effort?
> > Can
> > > > we have as a near goal to bring 1.0 planing ourselves to donate
some
> > > hours
> > > > to Apache Royale to make this happen? If some of us help in the
> current
> > > > state I think we can get to it sooner.
> > > >
> > > > Thanks
> > > >
> > > >
> > > > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > > > lazzari.angelo@gmail.com>)
> > > > escribió:
> > > >
> > > > > I am completely agree with Olaf: start using a new platform where
> the
> > > > > documentation is not complete, clean and updated it is a really
bad
> > > > > thing...and it would be a potential reason to increase the
> difficulty
> > > to
> > > > > adopt the platform...
> > > > >
> > > > > Angelo
> > > > >
> > > > > El vie., 26 abr. 2019 8:54, Olaf Krueger <ma...@olafkrueger.net>
> > > > escribió:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > Basically, I think it's important to provide a great developer
> > > > > experience.
> > > > > > IMO, that's more important than trying to implement missing
> > features.
> > > > > >
> > > > > > One thing to achieve this is documentation of course.
> > > > > > Thanks to all of you there already exist a lot of docs, but it
> > feels
> > > a
> > > > > bit
> > > > > > messy because they are hosted at different places, e.g.:
> > > > > >
> > > > > > - royale-docs repo
> > > > > > - royale-asjs wiki
> > > > > > - royale-asjs Readme
> > > > > > - https://royale.apache.org
> > > > > > - ...?
> > > > > >
> > > > > > As a user, it's hard to get an overview of what is available...
> and
> > > > > where.
> > > > > > Maybe it's a good idea to consolidate the docs before releasing
> > 1.0.
> > > > > >
> > > > > > Just my 2 cents,
> > > > > > Olaf
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Sent from:
http://apache-royale-development.20373.n8.nabble.com/
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > Carlos Rovira
> > > > http://about.me/carlosrovira
> > > >
> > >
> > >
> > > --
> > > Angelo Lazzari
> > > mobile: +34 683 137 087
> > > mail: lazzari.angelo@gmail.com
> > >
> > >
> > >
> > >
> >
>
------------------------------------------------------------------------------------------------------------------------
> > > Verify the correspondence of the addressee; otherwise, notify that to
> the
> > > sender and, conscious of the responsibility for the undue use,
destroy
> > the
> > > message and its copies.
> > >
> > >
> >
>
------------------------------------------------------------------------------------------------------------------------
> > >
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
> Angelo Lazzari
> mobile: +34 683 137 087
> mail: lazzari.angelo@gmail.com
>
>
>
>
------------------------------------------------------------------------------------------------------------------------
> Verify the correspondence of the addressee; otherwise, notify that to the
> sender and, conscious of the responsibility for the undue use, destroy
the
> message and its copies.
>
>
------------------------------------------------------------------------------------------------------------------------
>
--
Carlos Rovira
http://about.me/carlosrovira
----- Message from Alex Harui <ah...@adobe.com.INVALID> on Fri, 26 Apr
2019 16:02:19 +0000 -----
To: "dev@royale.apache.org"
<de...@royale.apache.org>
Subject: Re: Version property (was: Let's bump Royale
version to 1.0)
On 4/26/19, 4:29 AM, "Kessler CTR Mark J"
<ma...@usmc.mil.INVALID> wrote:
> So far, we have not had the release scripts properly generate the
right version number for the NPM artifacts.
This spurred a question for me. Is there a way to find out what
version number the SDK binaries are in code for Royale? Sort of like the
Flex SDK mx.core.FlexVersion or at least a build date?
Not at this time. IMO, runtime versioning wasn't worth the cost of all of
those strings and code in the production app. Also, Royale was designed
from the beginning to try to be "version-agnostic". By using
loose-coupling via Beads/PAYG/ValuesManager and lots of interfaces instead
of direct class references, there shouldn't be a need to deal with version
incompatibilities at runtime like Flex did with the Marshall Plan and
FlexVersion and more.
Flex had to care about version incompatibilities because the fundamental
base classes were not loosely-coupled. Flex HelloWorld was 128K not just
because UIComponent was huge, but because UIComponent pulled in other
classes as init-time strongly-coupled dependencies. A good thing to think
about as you write Royale framework code is, "can every dependency be
easily replaced"?
After we hit 1.0 (and hopefully find some volunteers to write regression
tests), then new APIs to existing classes will need to be considered
carefully and implemented in extensions. So there will be some extension
of IUIBase that has some new API instead of adding new APIs to IUIBase. I
have a personal preference to use long names instead of numbers, so the
extension will hopefully be called IUIBaseWithWhatever instead of IUIBase2.
If you are asking about build-time versioning, we haven't done anything
there either. As long as there is no impact on production apps I think it
is fine for folks to contribute something if there is a need.
My 2 cents,
-Alex
-Mark K
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com.INVALID]
Sent: Friday, April 26, 2019 2:44 AM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Let's bump Royale version to 1.0
I do not have an opinion on what technical/marketing criteria we use to
decide which release to call 1.0. I'm not working directly with
users/customers.
I do not currently have time/energy/budget to work on any of the things
folks think need to be done to get to 1.0 and barely have enough time to
work on getting the next release out. So someone else will have to supply
the time/energy/budget to get these tasks done.
I do have an opinion based on a practical aspect. So far, we have not
had the release scripts properly generate the right version number for the
NPM artifacts. That's why we've jumped from 0.9.4 to 0.9.6 and skipped
0.9.5. So I would say we should not call this next release 1.0 and wait
until the release automation can correctly version all artifacts with the
right version number before we pick one to call 1.0. With any luck I'll
get the automation running next week and will ask for someone to volunteer
to test drive it.
-Alex
----- Message from Apache Royale CI Server <ap...@gmail.com> on
Fri, 26 Apr 2019 21:49:11 +0000 (UTC) -----
To: dev@royale.apache.org
Subject: Release Step 001
Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins
\workspace\Royale_Release_Step_001 and run the following commands:
git push
git checkout release/0.9.6
git push -u origin release/0.9.6
You will need your Apache/Github username and 2FA token.
----- Message from Apache Royale CI Server <ap...@gmail.com> on
Fri, 26 Apr 2019 22:05:55 +0000 (UTC) -----
To: dev@royale.apache.org
Subject: Release Step 001a
Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins
\workspace\Royale_Release_Step_001a_If_Utils and run the following
commands:
git push
You will need your Apache/Github username and 2FA token.
----- Message from Apache Royale CI Server <ap...@gmail.com> on
Fri, 26 Apr 2019 22:29:43 +0000 (UTC) -----
To: dev@royale.apache.org
Subject: Release Step 002
Succeeded
Log in to the server, open a command prompt, change directory to C:\jenkins
\workspace\Royale_Release_Step_002 and run the following commands:
git push
git push origin org.apache.royale.compiler-0.9.6-rc1
You will need your Apache/Github username and 2FA token.
----- Message from Apache Royale CI Server <ap...@gmail.com> on
Fri, 26 Apr 2019 22:36:43 +0000 (UTC) -----
To: dev@royale.apache.org
Subject: Release Step 002a
Succeeded
Continue on to Release Step 003
----- Message from Apache Royale CI Server <ap...@gmail.com> on
Fri, 26 Apr 2019 22:46:49 +0000 (UTC) -----
To: dev@royale.apache.org
Subject: Release Step 003
Succeeded
1. If you are releasing the utils jars (compiler-jburg-types and
compiler-build-tools), Run:
ant -f releasesteps.xml Release_Step_003 -Dutils=true
-Drelease.version=0.9.6
Otherwise, Run:
ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
This will download the artifacts then unzip and compile the source
artifact.
2. Validate that the compiled artifacts match the downloaded artifacts.
3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign
-Drelease.version=0.9.6
This will PGP sign the source ZIP and compiled JARs
4. Then run ant -f releasesteps.xml Release_Step_003_Upload
-Drelease.version=0.9.6
This will upload the signed artifacts to Maven Release Staging. Do not
"Close" the staging repository until the other repos have been added.
----- Message from Apache Royale CI Server <ap...@gmail.com> on
Sat, 27 Apr 2019 03:57:52 +0000 (UTC) -----
To: dev@royale.apache.org
Subject: Build failed in Jenkins:
royale-asjs_MXTests #722
See <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/722/display/redirect
>
------------------------------------------
[...truncated 2.03 MB...]
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataGridModel.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/DataGridModel.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IState.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataDefinition.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IViewportModel.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/WrappedHTMLElement.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/DropLocation.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/errors/CursorError.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/TextLineMetrics.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/CSSStyleDeclaration.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/FocusEventConverter.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MethodDefinition.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/display/Graphics.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollControlBase.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/ListBase.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataProviderVirtualItemRendererMapper.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/WatcherBase.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImage.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/BrowserEvent.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/PanelModel.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/models/PanelModel.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IPopUp.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ButtonTestScript.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/scripts/ButtonTestScript.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBase.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateField.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/RoyaleContext.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ContainerBaseStrandChildren.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/UIUtils.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ListSingleSelectionMouseController.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuBarMouseController.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/controllers/MenuBarMouseController.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/CollectionEvent.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/menuClasses/MenuBarItemRenderer.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/accessories/PasswordInputBead.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/managers/ICursorManager.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/MenuBarTestScript.js
>
[mxmlc] using source file: <
http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/BaseListData.js
>
[mxmlc] using source file: <
Re: Let's bump Royale version to 1.0
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
no. I think we crossed the line some time ago and Royale is now a real and
usable technology.
But we did this issue [1] to talk about things still needed. One required
by Alex was MXRoyale, that seems to be on good way, other like CSS issues
was untouched (I tried to fix some, but with no success and couldn't get
responses to some threads open to guide me on it).
If 1.0 has a special meaning for others not so close to the project is that
"we open doors for all people to start using it" and that means to have
more responsibility to show the project is really valid for masses and
respond to some basic questions:
- "Do we have most of the documentation ready?" or, if people start
using it will find the most of the docs needed available. Don't think so,
just to put a random example, recently a user asked for compiler options,
and we still don't have that in our docs. I think we could solve this if
all people involved in Royale could spend some days working on it. But this
usually means Andrew and me.
- "Can we release each month or 2 months?", I don't think so. I tried
the release process and after the maven improvements that break the CI
steps in Nov-Dec, I tried to fix it with no success, while investing
several hours. I hope to reach again to that, and see what can I do to help
on that. Actually, while I'm pro to have ant and maven builds for users, I
don't understand why we are mixing that with the release process. I think
we are auto imposing an unnecessary burden with this requeriment. I think
release process could be greatly simplified if we just use maven, as many
other projects do (that's the actual way people are doing things, so doing
that way we're embracing a good practice). So users can build with Ant or
Maven (what they prefer), but we just need to release with maven on CI,
that is the natural tool to do that. I think that will solve this point
without problem, and will remove an actual huge barrier.
- Actual issues like in the issue [1]: Bindings (we are sponsoring Greg
this days to fix actual issues and create tests to make bindings
infrastructure more robust, that are what, in my experience, generates most
of the problems that appears to users at early stages in Royale) or some
Jewel issues are in the works today (Virtual DataGrid, Tree,...I need to
finish dark themes too). Other issues like CSS compiler problems, were
untouched
- I need to fix Moonshine mvn sdk compilation too
We already discussed most of this. We have just one bullet. If people
testing Royale has some solid point that Royale is not ok due to not have
enough docs, or having some issues with trying to build some example or
app, then we will have many problems to fix that feeling for people that
tries it.
For that reason, I'm for going naturally to 1.0 instead to bump.
That's what I mean/feel, but if others think we should go 1.0, then I'll
not oppose, but want to warn about it.
[1] https://github.com/apache/royale-asjs/issues/648
El mar., 18 feb. 2020 a las 9:57, Piotr Zarzycki (<pi...@gmail.com>)
escribió:
> Hi Carlos,
>
> Are you have in mind that Royale is not enough good for 1.0 ? I don't
> understand full what do you mean here.
>
> wt., 18 lut 2020 o 09:52 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
> > Hi Alex,
> > very good news. Congrats to all of you working on emulation! :).
> > There's as well other migration efforts based on Jewel and in good
> > progress, but with issues to manage over time. It could be a good time to
> > start trying to release, but I'll try to go 0.9.7 and continue improving
> > until release process could be really easy to do. As well docs continue
> to
> > be something we need if we want to have success for 1.0.
> >
> > El mar., 18 feb. 2020 a las 8:42, Alex Harui (<aharui@adobe.com.invalid
> >)
> > escribió:
> >
> > > Today, I received permission to disclose that Alina & Pashmina's team
> has
> > > 88 of their modules ready for release (tested and validated by their QA
> > > team). They still have more modules to migrate before they deliver to
> > > their customer, but it is a good sign that the emulation is sufficient
> > for
> > > many needs.
> > >
> > > Once I can merge the "has" branch and re-stabilize, I will hope that's
> > the
> > > last big change we need for a while. I have heard that there are other
> > > migration efforts underway using migration and I'm sure they will keep
> > > finding bugs, but I'm feeling better about the emulation code.
> > >
> > > -Alex
> > >
> > > On 12/18/19, 9:05 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> > >
> > > Every day, I hope to hear news that Alina & Pashmina or Serkan or
> > > somebody else has deployed a production app using the MXRoyale and/or
> > Spark
> > > Royale emulation components. But instead, I see more bugs being filed
> > for
> > > "obvious" things. You can look at the issues list of open and fixed
> > issues
> > > and the commits that fixed them to get a feel for it. Each of us has
> > their
> > > own threshold of how good a 1.0 version should be, so if more of you
> can
> > > look at these bugs and think it is ok for a 1.0 to have these problems,
> > > then great, let's release the next version as 1.0, but when I try to
> > > remember what Flex 1.0 was like, I think it didn't have these kinds of
> > > problems.
> > >
> > > As Carlos said below, we get one chance to make a good first
> > > impression, so I am being conservative. But it isn't my decision
> alone.
> > > It is really up to the rest of you.
> > >
> > > -Alex
> > >
> > > On 12/18/19, 6:41 AM, "Carlos Rovira" <ca...@apache.org>
> > wrote:
> > >
> > > Hi Piotr,
> > >
> > > I'm afraid my perception is that we need to get to 1.0 in a
> > > natural way. I
> > > mean: releasing 1.0 and giving exposure in all ways we can
> (webs,
> > > social
> > > media, magazines,...), means people will try us. If they try
> and
> > > fail, will
> > > never come back. So think about this as "only on bullet in your
> > > gun", if
> > > you fail de shot, that will be bad for all the work we are
> done.
> > > I'm ok to
> > > release 1.0 as soon as we see from "bird eye perspective" that
> > all
> > > things
> > > work as we expect.
> > >
> > > For me that things are:
> > >
> > > * Documentation will need to have at least some missing pages
> of
> > > features
> > > like: DataBindnig, Loading External Data (HTTPSerice,
> > > RemoteObject, JSON),
> > > View States, Item Renderers. Things like this are essential.
> > > * Emulation components need to be in a shape that allow
> > migrations
> > > in a
> > > good degree. I think people approaching direct migration with
> > > emulation
> > > components will many issues. I don't take into account look and
> > > feel of
> > > emulation components, just functionality and working from a
> flex
> > > code
> > > perspective, and just normal use cases with MX/Spark code, not
> > > third party
> > > libraries that we have no control over. Simple apps like TDF,
> and
> > > examples
> > > should work.
> > >
> > > If we decided we want to bypass the previous, at least we need
> to
> > > ensure
> > > "first try" of Royale for a newcomer (someone that knows very
> few
> > > about the
> > > tech) is successful. This is most important things of all. The
> > > other two
> > > are needed if we want people does not get frustrated and have
> > > solutions on
> > > their own and stay with us. The opposite is people can have a
> > > first try
> > > successful but abandon Royale due to unfinished things.
> > >
> > > I think 0.9.7-SNAPSHOT captures in a realistic number where we
> > are.
> > > Technology works, and most people using it now can do lots of
> > > things, but
> > > we still need to cover some things to reach that 1.0. We are
> not
> > > too far
> > > but I think is still some month in the future.
> > >
> > > just my 2 :)
> > >
> > > Carlos
> > >
> > >
> > >
> > >
> > > El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
> > > piotrzarzycki21@gmail.com>) escribió:
> > >
> > > > Hello,
> > > >
> > > > This thread is old and this was the last message from me.
> What
> > > has changed
> > > > on your end guys ?
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <
> > > piotrzarzycki21@gmail.com>
> > > > napisał(a):
> > > >
> > > > > Hi Guys,
> > > > >
> > > > > Thank you so far for a great discussion. I see that there
> is
> > > an obvious
> > > > > needs to improve documentation the most.
> > > > >
> > > > > I would like to express my personal feelings regarding
> > > releasing anything
> > > > > what is not 1.0 after 0.9.6. Based on my experience with
> this
> > > project I
> > > > > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc.
> will
> > > take less
> > > > than
> > > > > 6-8 months form now on. Even if we will have automatic
> > release
> > > process I
> > > > > cannot believe that is going to happen in a less time than
> I
> > > mention.
> > > > >
> > > > > Why I'm thinking like that:
> > > > > - Justin just provided to the contributors generous offer -
> > > it's been
> > > > > couple of days and there is absolutely no response.
> > > > > - I've seen as part of the responses some concrete issues
> > > towards code in
> > > > > SDK. I don't believe that there will be anyone who fix them
> > > UNLESS
> > > > someone
> > > > > need that stuff in his application which has been under
> > > development in
> > > > his
> > > > > daily job. Which leads me to conclusion that we will wait
> > > months before
> > > > > anything from that list will be fixed.
> > > > >
> > > > > How Royale is going on right now?
> > > > > In my original email I expressed that it is enough good to
> > > bump it to 1.0
> > > > > - which gets us more credibility and push us to a better
> > > light. I got
> > > > clear
> > > > > responses from community that the only thing which is in
> the
> > > way of to
> > > > 1.0
> > > > > is documentation.
> > > > >
> > > > > W have one production app in Royale, another one has been
> > > created by
> > > > > Carlos. I'm working on the third one. Justin mention fourth
> > > one which I'm
> > > > > reviewing right now because it is written in Flex - it
> looks
> > > there won't
> > > > be
> > > > > problem with porting to Royale. To me it is enough proof
> that
> > > Royale is
> > > > as
> > > > > good as is to expose itself for more wider audience.
> Because
> > > this is
> > > > > exactly what will happen when we bump to that magic 1.0.
> > > > > People on this project are talking about community, my
> > > proposition to
> > > > bump
> > > > > Royale to 1.0 is towards community with hope that it helps
> > > grow thanks to
> > > > > that step. With hope that finally I will see on the list
> more
> > > people,
> > > > with
> > > > > hope that I will see someone who doesn't have background in
> > > ActionScript,
> > > > > but was curious about the project.
> > > > >
> > > > > In this thread I don't see rejection to my idea, so I'm
> going
> > > to work to
> > > > > improve some areas and start release with bumped version to
> > > 1.0, whether
> > > > it
> > > > > will be after 0.9.7, 0.9.8 it doesn't matter - What's
> really
> > > matter is
> > > > that
> > > > > we are not facing in current version any walls during
> > > development, so
> > > > this
> > > > > is enough to me giving that framework 1.0.
> > > > >
> > > > > Thanks,
> > > > > Piotr
> > > > >
> > > > > pon., 29 kwi 2019 o 19:44 Carlos Rovira <
> > > carlosrovira@apache.org>
> > > > > napisał(a):
> > > > >
> > > > >> Hi Justin,
> > > > >>
> > > > >> great initiative, but some thoughts:
> > > > >>
> > > > >> 1.- As Olaf said, Alex or I are just two more devs, so we
> > can
> > > say what
> > > > >> should we do. That's the apache way! :), only work towards
> > > the goal and
> > > > >> giving advice to make things happen. We decisions are
> > > community managed
> > > > >>
> > > > >> 2.- I think is very generous offer so people can
> contribute
> > > and earn
> > > > some
> > > > >> money and a great plan,
> > > > >>
> > > > >> Some things you should take into account for the rewarding
> > > plan:
> > > > >>
> > > > >> * We just get results of the poll about releasing
> published
> > > few minutes
> > > > >> ago. Seems people wants to focus docs first and release
> > > second (from 61
> > > > >> votes).
> > > > >> * In the other hand, I see Alex is still fighting with the
> > > release
> > > > >> process.
> > > > >> He stated that probably this week he will have the process
> > > ready to be
> > > > >> tested by someone.
> > > > >> If he get to that point that will be awesome, and hope
> > others
> > > could be
> > > > the
> > > > >> first one in try to "push the button". If that works ok,
> > > we'll have a
> > > > >> 0.9.6
> > > > >> release (I think the one by Alex), and then a 0.9.7 (by
> that
> > > new release
> > > > >> manager). At that point, I figure we can plan 0.9.8, 0.9.9
> > > and Finlay
> > > > 1.0.
> > > > >> For me release should happen at least from month to month.
> > > have sense?
> > > > >>
> > > > >> Just my my thoughts, but hope other want to share here
> what
> > > they can do
> > > > >> and
> > > > >> work to earn some money too! :)
> > > > >>
> > > > >>
> > > > >>
> > > > >> >
> > > > >> > --
> > > > >> > Carlos Rovira
> > > > >> >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >> >
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > >
> > > > > Piotr Zarzycki
> > > > >
> > > > > Patreon: *
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > > > <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > >*
> > > > >
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > > <
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > >*
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > >
> > >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> > >
> > >
> > >
> > >
> > >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Let's bump Royale version to 1.0
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Carlos,
Are you have in mind that Royale is not enough good for 1.0 ? I don't
understand full what do you mean here.
wt., 18 lut 2020 o 09:52 Carlos Rovira <ca...@apache.org> napisał(a):
> Hi Alex,
> very good news. Congrats to all of you working on emulation! :).
> There's as well other migration efforts based on Jewel and in good
> progress, but with issues to manage over time. It could be a good time to
> start trying to release, but I'll try to go 0.9.7 and continue improving
> until release process could be really easy to do. As well docs continue to
> be something we need if we want to have success for 1.0.
>
> El mar., 18 feb. 2020 a las 8:42, Alex Harui (<ah...@adobe.com.invalid>)
> escribió:
>
> > Today, I received permission to disclose that Alina & Pashmina's team has
> > 88 of their modules ready for release (tested and validated by their QA
> > team). They still have more modules to migrate before they deliver to
> > their customer, but it is a good sign that the emulation is sufficient
> for
> > many needs.
> >
> > Once I can merge the "has" branch and re-stabilize, I will hope that's
> the
> > last big change we need for a while. I have heard that there are other
> > migration efforts underway using migration and I'm sure they will keep
> > finding bugs, but I'm feeling better about the emulation code.
> >
> > -Alex
> >
> > On 12/18/19, 9:05 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
> >
> > Every day, I hope to hear news that Alina & Pashmina or Serkan or
> > somebody else has deployed a production app using the MXRoyale and/or
> Spark
> > Royale emulation components. But instead, I see more bugs being filed
> for
> > "obvious" things. You can look at the issues list of open and fixed
> issues
> > and the commits that fixed them to get a feel for it. Each of us has
> their
> > own threshold of how good a 1.0 version should be, so if more of you can
> > look at these bugs and think it is ok for a 1.0 to have these problems,
> > then great, let's release the next version as 1.0, but when I try to
> > remember what Flex 1.0 was like, I think it didn't have these kinds of
> > problems.
> >
> > As Carlos said below, we get one chance to make a good first
> > impression, so I am being conservative. But it isn't my decision alone.
> > It is really up to the rest of you.
> >
> > -Alex
> >
> > On 12/18/19, 6:41 AM, "Carlos Rovira" <ca...@apache.org>
> wrote:
> >
> > Hi Piotr,
> >
> > I'm afraid my perception is that we need to get to 1.0 in a
> > natural way. I
> > mean: releasing 1.0 and giving exposure in all ways we can (webs,
> > social
> > media, magazines,...), means people will try us. If they try and
> > fail, will
> > never come back. So think about this as "only on bullet in your
> > gun", if
> > you fail de shot, that will be bad for all the work we are done.
> > I'm ok to
> > release 1.0 as soon as we see from "bird eye perspective" that
> all
> > things
> > work as we expect.
> >
> > For me that things are:
> >
> > * Documentation will need to have at least some missing pages of
> > features
> > like: DataBindnig, Loading External Data (HTTPSerice,
> > RemoteObject, JSON),
> > View States, Item Renderers. Things like this are essential.
> > * Emulation components need to be in a shape that allow
> migrations
> > in a
> > good degree. I think people approaching direct migration with
> > emulation
> > components will many issues. I don't take into account look and
> > feel of
> > emulation components, just functionality and working from a flex
> > code
> > perspective, and just normal use cases with MX/Spark code, not
> > third party
> > libraries that we have no control over. Simple apps like TDF, and
> > examples
> > should work.
> >
> > If we decided we want to bypass the previous, at least we need to
> > ensure
> > "first try" of Royale for a newcomer (someone that knows very few
> > about the
> > tech) is successful. This is most important things of all. The
> > other two
> > are needed if we want people does not get frustrated and have
> > solutions on
> > their own and stay with us. The opposite is people can have a
> > first try
> > successful but abandon Royale due to unfinished things.
> >
> > I think 0.9.7-SNAPSHOT captures in a realistic number where we
> are.
> > Technology works, and most people using it now can do lots of
> > things, but
> > we still need to cover some things to reach that 1.0. We are not
> > too far
> > but I think is still some month in the future.
> >
> > just my 2 :)
> >
> > Carlos
> >
> >
> >
> >
> > El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
> > piotrzarzycki21@gmail.com>) escribió:
> >
> > > Hello,
> > >
> > > This thread is old and this was the last message from me. What
> > has changed
> > > on your end guys ?
> > >
> > > Thanks,
> > > Piotr
> > >
> > > wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <
> > piotrzarzycki21@gmail.com>
> > > napisał(a):
> > >
> > > > Hi Guys,
> > > >
> > > > Thank you so far for a great discussion. I see that there is
> > an obvious
> > > > needs to improve documentation the most.
> > > >
> > > > I would like to express my personal feelings regarding
> > releasing anything
> > > > what is not 1.0 after 0.9.6. Based on my experience with this
> > project I
> > > > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will
> > take less
> > > than
> > > > 6-8 months form now on. Even if we will have automatic
> release
> > process I
> > > > cannot believe that is going to happen in a less time than I
> > mention.
> > > >
> > > > Why I'm thinking like that:
> > > > - Justin just provided to the contributors generous offer -
> > it's been
> > > > couple of days and there is absolutely no response.
> > > > - I've seen as part of the responses some concrete issues
> > towards code in
> > > > SDK. I don't believe that there will be anyone who fix them
> > UNLESS
> > > someone
> > > > need that stuff in his application which has been under
> > development in
> > > his
> > > > daily job. Which leads me to conclusion that we will wait
> > months before
> > > > anything from that list will be fixed.
> > > >
> > > > How Royale is going on right now?
> > > > In my original email I expressed that it is enough good to
> > bump it to 1.0
> > > > - which gets us more credibility and push us to a better
> > light. I got
> > > clear
> > > > responses from community that the only thing which is in the
> > way of to
> > > 1.0
> > > > is documentation.
> > > >
> > > > W have one production app in Royale, another one has been
> > created by
> > > > Carlos. I'm working on the third one. Justin mention fourth
> > one which I'm
> > > > reviewing right now because it is written in Flex - it looks
> > there won't
> > > be
> > > > problem with porting to Royale. To me it is enough proof that
> > Royale is
> > > as
> > > > good as is to expose itself for more wider audience. Because
> > this is
> > > > exactly what will happen when we bump to that magic 1.0.
> > > > People on this project are talking about community, my
> > proposition to
> > > bump
> > > > Royale to 1.0 is towards community with hope that it helps
> > grow thanks to
> > > > that step. With hope that finally I will see on the list more
> > people,
> > > with
> > > > hope that I will see someone who doesn't have background in
> > ActionScript,
> > > > but was curious about the project.
> > > >
> > > > In this thread I don't see rejection to my idea, so I'm going
> > to work to
> > > > improve some areas and start release with bumped version to
> > 1.0, whether
> > > it
> > > > will be after 0.9.7, 0.9.8 it doesn't matter - What's really
> > matter is
> > > that
> > > > we are not facing in current version any walls during
> > development, so
> > > this
> > > > is enough to me giving that framework 1.0.
> > > >
> > > > Thanks,
> > > > Piotr
> > > >
> > > > pon., 29 kwi 2019 o 19:44 Carlos Rovira <
> > carlosrovira@apache.org>
> > > > napisał(a):
> > > >
> > > >> Hi Justin,
> > > >>
> > > >> great initiative, but some thoughts:
> > > >>
> > > >> 1.- As Olaf said, Alex or I are just two more devs, so we
> can
> > say what
> > > >> should we do. That's the apache way! :), only work towards
> > the goal and
> > > >> giving advice to make things happen. We decisions are
> > community managed
> > > >>
> > > >> 2.- I think is very generous offer so people can contribute
> > and earn
> > > some
> > > >> money and a great plan,
> > > >>
> > > >> Some things you should take into account for the rewarding
> > plan:
> > > >>
> > > >> * We just get results of the poll about releasing published
> > few minutes
> > > >> ago. Seems people wants to focus docs first and release
> > second (from 61
> > > >> votes).
> > > >> * In the other hand, I see Alex is still fighting with the
> > release
> > > >> process.
> > > >> He stated that probably this week he will have the process
> > ready to be
> > > >> tested by someone.
> > > >> If he get to that point that will be awesome, and hope
> others
> > could be
> > > the
> > > >> first one in try to "push the button". If that works ok,
> > we'll have a
> > > >> 0.9.6
> > > >> release (I think the one by Alex), and then a 0.9.7 (by that
> > new release
> > > >> manager). At that point, I figure we can plan 0.9.8, 0.9.9
> > and Finlay
> > > 1.0.
> > > >> For me release should happen at least from month to month.
> > have sense?
> > > >>
> > > >> Just my my thoughts, but hope other want to share here what
> > they can do
> > > >> and
> > > >> work to earn some money too! :)
> > > >>
> > > >>
> > > >>
> > > >> >
> > > >> > --
> > > >> > Carlos Rovira
> > > >> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> > > >> >
> > > >> >
> > > >> >
> > > >> >
> > > >>
> > > >
> > > >
> > > > --
> > > >
> > > > Piotr Zarzycki
> > > >
> > > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > >*
> > > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > <
> >
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > >*
> > >
> >
> >
> > --
> > Carlos Rovira
> >
> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> >
> >
> >
> >
> >
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Let's bump Royale version to 1.0
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex,
very good news. Congrats to all of you working on emulation! :).
There's as well other migration efforts based on Jewel and in good
progress, but with issues to manage over time. It could be a good time to
start trying to release, but I'll try to go 0.9.7 and continue improving
until release process could be really easy to do. As well docs continue to
be something we need if we want to have success for 1.0.
El mar., 18 feb. 2020 a las 8:42, Alex Harui (<ah...@adobe.com.invalid>)
escribió:
> Today, I received permission to disclose that Alina & Pashmina's team has
> 88 of their modules ready for release (tested and validated by their QA
> team). They still have more modules to migrate before they deliver to
> their customer, but it is a good sign that the emulation is sufficient for
> many needs.
>
> Once I can merge the "has" branch and re-stabilize, I will hope that's the
> last big change we need for a while. I have heard that there are other
> migration efforts underway using migration and I'm sure they will keep
> finding bugs, but I'm feeling better about the emulation code.
>
> -Alex
>
> On 12/18/19, 9:05 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> Every day, I hope to hear news that Alina & Pashmina or Serkan or
> somebody else has deployed a production app using the MXRoyale and/or Spark
> Royale emulation components. But instead, I see more bugs being filed for
> "obvious" things. You can look at the issues list of open and fixed issues
> and the commits that fixed them to get a feel for it. Each of us has their
> own threshold of how good a 1.0 version should be, so if more of you can
> look at these bugs and think it is ok for a 1.0 to have these problems,
> then great, let's release the next version as 1.0, but when I try to
> remember what Flex 1.0 was like, I think it didn't have these kinds of
> problems.
>
> As Carlos said below, we get one chance to make a good first
> impression, so I am being conservative. But it isn't my decision alone.
> It is really up to the rest of you.
>
> -Alex
>
> On 12/18/19, 6:41 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Piotr,
>
> I'm afraid my perception is that we need to get to 1.0 in a
> natural way. I
> mean: releasing 1.0 and giving exposure in all ways we can (webs,
> social
> media, magazines,...), means people will try us. If they try and
> fail, will
> never come back. So think about this as "only on bullet in your
> gun", if
> you fail de shot, that will be bad for all the work we are done.
> I'm ok to
> release 1.0 as soon as we see from "bird eye perspective" that all
> things
> work as we expect.
>
> For me that things are:
>
> * Documentation will need to have at least some missing pages of
> features
> like: DataBindnig, Loading External Data (HTTPSerice,
> RemoteObject, JSON),
> View States, Item Renderers. Things like this are essential.
> * Emulation components need to be in a shape that allow migrations
> in a
> good degree. I think people approaching direct migration with
> emulation
> components will many issues. I don't take into account look and
> feel of
> emulation components, just functionality and working from a flex
> code
> perspective, and just normal use cases with MX/Spark code, not
> third party
> libraries that we have no control over. Simple apps like TDF, and
> examples
> should work.
>
> If we decided we want to bypass the previous, at least we need to
> ensure
> "first try" of Royale for a newcomer (someone that knows very few
> about the
> tech) is successful. This is most important things of all. The
> other two
> are needed if we want people does not get frustrated and have
> solutions on
> their own and stay with us. The opposite is people can have a
> first try
> successful but abandon Royale due to unfinished things.
>
> I think 0.9.7-SNAPSHOT captures in a realistic number where we are.
> Technology works, and most people using it now can do lots of
> things, but
> we still need to cover some things to reach that 1.0. We are not
> too far
> but I think is still some month in the future.
>
> just my 2 :)
>
> Carlos
>
>
>
>
> El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Hello,
> >
> > This thread is old and this was the last message from me. What
> has changed
> > on your end guys ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <
> piotrzarzycki21@gmail.com>
> > napisał(a):
> >
> > > Hi Guys,
> > >
> > > Thank you so far for a great discussion. I see that there is
> an obvious
> > > needs to improve documentation the most.
> > >
> > > I would like to express my personal feelings regarding
> releasing anything
> > > what is not 1.0 after 0.9.6. Based on my experience with this
> project I
> > > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will
> take less
> > than
> > > 6-8 months form now on. Even if we will have automatic release
> process I
> > > cannot believe that is going to happen in a less time than I
> mention.
> > >
> > > Why I'm thinking like that:
> > > - Justin just provided to the contributors generous offer -
> it's been
> > > couple of days and there is absolutely no response.
> > > - I've seen as part of the responses some concrete issues
> towards code in
> > > SDK. I don't believe that there will be anyone who fix them
> UNLESS
> > someone
> > > need that stuff in his application which has been under
> development in
> > his
> > > daily job. Which leads me to conclusion that we will wait
> months before
> > > anything from that list will be fixed.
> > >
> > > How Royale is going on right now?
> > > In my original email I expressed that it is enough good to
> bump it to 1.0
> > > - which gets us more credibility and push us to a better
> light. I got
> > clear
> > > responses from community that the only thing which is in the
> way of to
> > 1.0
> > > is documentation.
> > >
> > > W have one production app in Royale, another one has been
> created by
> > > Carlos. I'm working on the third one. Justin mention fourth
> one which I'm
> > > reviewing right now because it is written in Flex - it looks
> there won't
> > be
> > > problem with porting to Royale. To me it is enough proof that
> Royale is
> > as
> > > good as is to expose itself for more wider audience. Because
> this is
> > > exactly what will happen when we bump to that magic 1.0.
> > > People on this project are talking about community, my
> proposition to
> > bump
> > > Royale to 1.0 is towards community with hope that it helps
> grow thanks to
> > > that step. With hope that finally I will see on the list more
> people,
> > with
> > > hope that I will see someone who doesn't have background in
> ActionScript,
> > > but was curious about the project.
> > >
> > > In this thread I don't see rejection to my idea, so I'm going
> to work to
> > > improve some areas and start release with bumped version to
> 1.0, whether
> > it
> > > will be after 0.9.7, 0.9.8 it doesn't matter - What's really
> matter is
> > that
> > > we are not facing in current version any walls during
> development, so
> > this
> > > is enough to me giving that framework 1.0.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 29 kwi 2019 o 19:44 Carlos Rovira <
> carlosrovira@apache.org>
> > > napisał(a):
> > >
> > >> Hi Justin,
> > >>
> > >> great initiative, but some thoughts:
> > >>
> > >> 1.- As Olaf said, Alex or I are just two more devs, so we can
> say what
> > >> should we do. That's the apache way! :), only work towards
> the goal and
> > >> giving advice to make things happen. We decisions are
> community managed
> > >>
> > >> 2.- I think is very generous offer so people can contribute
> and earn
> > some
> > >> money and a great plan,
> > >>
> > >> Some things you should take into account for the rewarding
> plan:
> > >>
> > >> * We just get results of the poll about releasing published
> few minutes
> > >> ago. Seems people wants to focus docs first and release
> second (from 61
> > >> votes).
> > >> * In the other hand, I see Alex is still fighting with the
> release
> > >> process.
> > >> He stated that probably this week he will have the process
> ready to be
> > >> tested by someone.
> > >> If he get to that point that will be awesome, and hope others
> could be
> > the
> > >> first one in try to "push the button". If that works ok,
> we'll have a
> > >> 0.9.6
> > >> release (I think the one by Alex), and then a 0.9.7 (by that
> new release
> > >> manager). At that point, I figure we can plan 0.9.8, 0.9.9
> and Finlay
> > 1.0.
> > >> For me release should happen at least from month to month.
> have sense?
> > >>
> > >> Just my my thoughts, but hope other want to share here what
> they can do
> > >> and
> > >> work to earn some money too! :)
> > >>
> > >>
> > >>
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> >
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> >*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > <
> https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> >*
> >
>
>
> --
> Carlos Rovira
>
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
>
>
>
>
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Let's bump Royale version to 1.0
Posted by Serkan Taş <se...@likyateknoloji.com>.
Congratulations Alex,
Serkan...
18.02.2020 10:42 tarihinde Alex Harui yazdı:
> Today, I received permission to disclose that Alina & Pashmina's team has 88 of their modules ready for release (tested and validated by their QA team). They still have more modules to migrate before they deliver to their customer, but it is a good sign that the emulation is sufficient for many needs.
>
> Once I can merge the "has" branch and re-stabilize, I will hope that's the last big change we need for a while. I have heard that there are other migration efforts underway using migration and I'm sure they will keep finding bugs, but I'm feeling better about the emulation code.
>
> -Alex
>
> On 12/18/19, 9:05 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
>
> Every day, I hope to hear news that Alina & Pashmina or Serkan or somebody else has deployed a production app using the MXRoyale and/or Spark Royale emulation components. But instead, I see more bugs being filed for "obvious" things. You can look at the issues list of open and fixed issues and the commits that fixed them to get a feel for it. Each of us has their own threshold of how good a 1.0 version should be, so if more of you can look at these bugs and think it is ok for a 1.0 to have these problems, then great, let's release the next version as 1.0, but when I try to remember what Flex 1.0 was like, I think it didn't have these kinds of problems.
>
> As Carlos said below, we get one chance to make a good first impression, so I am being conservative. But it isn't my decision alone. It is really up to the rest of you.
>
> -Alex
>
> On 12/18/19, 6:41 AM, "Carlos Rovira" <ca...@apache.org> wrote:
>
> Hi Piotr,
>
> I'm afraid my perception is that we need to get to 1.0 in a natural way. I
> mean: releasing 1.0 and giving exposure in all ways we can (webs, social
> media, magazines,...), means people will try us. If they try and fail, will
> never come back. So think about this as "only on bullet in your gun", if
> you fail de shot, that will be bad for all the work we are done. I'm ok to
> release 1.0 as soon as we see from "bird eye perspective" that all things
> work as we expect.
>
> For me that things are:
>
> * Documentation will need to have at least some missing pages of features
> like: DataBindnig, Loading External Data (HTTPSerice, RemoteObject, JSON),
> View States, Item Renderers. Things like this are essential.
> * Emulation components need to be in a shape that allow migrations in a
> good degree. I think people approaching direct migration with emulation
> components will many issues. I don't take into account look and feel of
> emulation components, just functionality and working from a flex code
> perspective, and just normal use cases with MX/Spark code, not third party
> libraries that we have no control over. Simple apps like TDF, and examples
> should work.
>
> If we decided we want to bypass the previous, at least we need to ensure
> "first try" of Royale for a newcomer (someone that knows very few about the
> tech) is successful. This is most important things of all. The other two
> are needed if we want people does not get frustrated and have solutions on
> their own and stay with us. The opposite is people can have a first try
> successful but abandon Royale due to unfinished things.
>
> I think 0.9.7-SNAPSHOT captures in a realistic number where we are.
> Technology works, and most people using it now can do lots of things, but
> we still need to cover some things to reach that 1.0. We are not too far
> but I think is still some month in the future.
>
> just my 2 :)
>
> Carlos
>
>
>
>
> El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
> piotrzarzycki21@gmail.com>) escribió:
>
> > Hello,
> >
> > This thread is old and this was the last message from me. What has changed
> > on your end guys ?
> >
> > Thanks,
> > Piotr
> >
> > wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <pi...@gmail.com>
> > napisał(a):
> >
> > > Hi Guys,
> > >
> > > Thank you so far for a great discussion. I see that there is an obvious
> > > needs to improve documentation the most.
> > >
> > > I would like to express my personal feelings regarding releasing anything
> > > what is not 1.0 after 0.9.6. Based on my experience with this project I
> > > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less
> > than
> > > 6-8 months form now on. Even if we will have automatic release process I
> > > cannot believe that is going to happen in a less time than I mention.
> > >
> > > Why I'm thinking like that:
> > > - Justin just provided to the contributors generous offer - it's been
> > > couple of days and there is absolutely no response.
> > > - I've seen as part of the responses some concrete issues towards code in
> > > SDK. I don't believe that there will be anyone who fix them UNLESS
> > someone
> > > need that stuff in his application which has been under development in
> > his
> > > daily job. Which leads me to conclusion that we will wait months before
> > > anything from that list will be fixed.
> > >
> > > How Royale is going on right now?
> > > In my original email I expressed that it is enough good to bump it to 1.0
> > > - which gets us more credibility and push us to a better light. I got
> > clear
> > > responses from community that the only thing which is in the way of to
> > 1.0
> > > is documentation.
> > >
> > > W have one production app in Royale, another one has been created by
> > > Carlos. I'm working on the third one. Justin mention fourth one which I'm
> > > reviewing right now because it is written in Flex - it looks there won't
> > be
> > > problem with porting to Royale. To me it is enough proof that Royale is
> > as
> > > good as is to expose itself for more wider audience. Because this is
> > > exactly what will happen when we bump to that magic 1.0.
> > > People on this project are talking about community, my proposition to
> > bump
> > > Royale to 1.0 is towards community with hope that it helps grow thanks to
> > > that step. With hope that finally I will see on the list more people,
> > with
> > > hope that I will see someone who doesn't have background in ActionScript,
> > > but was curious about the project.
> > >
> > > In this thread I don't see rejection to my idea, so I'm going to work to
> > > improve some areas and start release with bumped version to 1.0, whether
> > it
> > > will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is
> > that
> > > we are not facing in current version any walls during development, so
> > this
> > > is enough to me giving that framework 1.0.
> > >
> > > Thanks,
> > > Piotr
> > >
> > > pon., 29 kwi 2019 o 19:44 Carlos Rovira <ca...@apache.org>
> > > napisał(a):
> > >
> > >> Hi Justin,
> > >>
> > >> great initiative, but some thoughts:
> > >>
> > >> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
> > >> should we do. That's the apache way! :), only work towards the goal and
> > >> giving advice to make things happen. We decisions are community managed
> > >>
> > >> 2.- I think is very generous offer so people can contribute and earn
> > some
> > >> money and a great plan,
> > >>
> > >> Some things you should take into account for the rewarding plan:
> > >>
> > >> * We just get results of the poll about releasing published few minutes
> > >> ago. Seems people wants to focus docs first and release second (from 61
> > >> votes).
> > >> * In the other hand, I see Alex is still fighting with the release
> > >> process.
> > >> He stated that probably this week he will have the process ready to be
> > >> tested by someone.
> > >> If he get to that point that will be awesome, and hope others could be
> > the
> > >> first one in try to "push the button". If that works ok, we'll have a
> > >> 0.9.6
> > >> release (I think the one by Alex), and then a 0.9.7 (by that new release
> > >> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay
> > 1.0.
> > >> For me release should happen at least from month to month. have sense?
> > >>
> > >> Just my my thoughts, but hope other want to share here what they can do
> > >> and
> > >> work to earn some money too! :)
> > >>
> > >>
> > >>
> > >> >
> > >> > --
> > >> > Carlos Rovira
> > >> > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> > >> >
> > >> >
> > >> >
> > >> >
> > >>
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0>*
> > >
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0>*
> >
>
>
> --
> Carlos Rovira
> https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
>
>
>
>
Re: Let's bump Royale version to 1.0
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Today, I received permission to disclose that Alina & Pashmina's team has 88 of their modules ready for release (tested and validated by their QA team). They still have more modules to migrate before they deliver to their customer, but it is a good sign that the emulation is sufficient for many needs.
Once I can merge the "has" branch and re-stabilize, I will hope that's the last big change we need for a while. I have heard that there are other migration efforts underway using migration and I'm sure they will keep finding bugs, but I'm feeling better about the emulation code.
-Alex
On 12/18/19, 9:05 AM, "Alex Harui" <ah...@adobe.com.INVALID> wrote:
Every day, I hope to hear news that Alina & Pashmina or Serkan or somebody else has deployed a production app using the MXRoyale and/or Spark Royale emulation components. But instead, I see more bugs being filed for "obvious" things. You can look at the issues list of open and fixed issues and the commits that fixed them to get a feel for it. Each of us has their own threshold of how good a 1.0 version should be, so if more of you can look at these bugs and think it is ok for a 1.0 to have these problems, then great, let's release the next version as 1.0, but when I try to remember what Flex 1.0 was like, I think it didn't have these kinds of problems.
As Carlos said below, we get one chance to make a good first impression, so I am being conservative. But it isn't my decision alone. It is really up to the rest of you.
-Alex
On 12/18/19, 6:41 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Piotr,
I'm afraid my perception is that we need to get to 1.0 in a natural way. I
mean: releasing 1.0 and giving exposure in all ways we can (webs, social
media, magazines,...), means people will try us. If they try and fail, will
never come back. So think about this as "only on bullet in your gun", if
you fail de shot, that will be bad for all the work we are done. I'm ok to
release 1.0 as soon as we see from "bird eye perspective" that all things
work as we expect.
For me that things are:
* Documentation will need to have at least some missing pages of features
like: DataBindnig, Loading External Data (HTTPSerice, RemoteObject, JSON),
View States, Item Renderers. Things like this are essential.
* Emulation components need to be in a shape that allow migrations in a
good degree. I think people approaching direct migration with emulation
components will many issues. I don't take into account look and feel of
emulation components, just functionality and working from a flex code
perspective, and just normal use cases with MX/Spark code, not third party
libraries that we have no control over. Simple apps like TDF, and examples
should work.
If we decided we want to bypass the previous, at least we need to ensure
"first try" of Royale for a newcomer (someone that knows very few about the
tech) is successful. This is most important things of all. The other two
are needed if we want people does not get frustrated and have solutions on
their own and stay with us. The opposite is people can have a first try
successful but abandon Royale due to unfinished things.
I think 0.9.7-SNAPSHOT captures in a realistic number where we are.
Technology works, and most people using it now can do lots of things, but
we still need to cover some things to reach that 1.0. We are not too far
but I think is still some month in the future.
just my 2 :)
Carlos
El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hello,
>
> This thread is old and this was the last message from me. What has changed
> on your end guys ?
>
> Thanks,
> Piotr
>
> wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Guys,
> >
> > Thank you so far for a great discussion. I see that there is an obvious
> > needs to improve documentation the most.
> >
> > I would like to express my personal feelings regarding releasing anything
> > what is not 1.0 after 0.9.6. Based on my experience with this project I
> > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less
> than
> > 6-8 months form now on. Even if we will have automatic release process I
> > cannot believe that is going to happen in a less time than I mention.
> >
> > Why I'm thinking like that:
> > - Justin just provided to the contributors generous offer - it's been
> > couple of days and there is absolutely no response.
> > - I've seen as part of the responses some concrete issues towards code in
> > SDK. I don't believe that there will be anyone who fix them UNLESS
> someone
> > need that stuff in his application which has been under development in
> his
> > daily job. Which leads me to conclusion that we will wait months before
> > anything from that list will be fixed.
> >
> > How Royale is going on right now?
> > In my original email I expressed that it is enough good to bump it to 1.0
> > - which gets us more credibility and push us to a better light. I got
> clear
> > responses from community that the only thing which is in the way of to
> 1.0
> > is documentation.
> >
> > W have one production app in Royale, another one has been created by
> > Carlos. I'm working on the third one. Justin mention fourth one which I'm
> > reviewing right now because it is written in Flex - it looks there won't
> be
> > problem with porting to Royale. To me it is enough proof that Royale is
> as
> > good as is to expose itself for more wider audience. Because this is
> > exactly what will happen when we bump to that magic 1.0.
> > People on this project are talking about community, my proposition to
> bump
> > Royale to 1.0 is towards community with hope that it helps grow thanks to
> > that step. With hope that finally I will see on the list more people,
> with
> > hope that I will see someone who doesn't have background in ActionScript,
> > but was curious about the project.
> >
> > In this thread I don't see rejection to my idea, so I'm going to work to
> > improve some areas and start release with bumped version to 1.0, whether
> it
> > will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is
> that
> > we are not facing in current version any walls during development, so
> this
> > is enough to me giving that framework 1.0.
> >
> > Thanks,
> > Piotr
> >
> > pon., 29 kwi 2019 o 19:44 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Hi Justin,
> >>
> >> great initiative, but some thoughts:
> >>
> >> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
> >> should we do. That's the apache way! :), only work towards the goal and
> >> giving advice to make things happen. We decisions are community managed
> >>
> >> 2.- I think is very generous offer so people can contribute and earn
> some
> >> money and a great plan,
> >>
> >> Some things you should take into account for the rewarding plan:
> >>
> >> * We just get results of the poll about releasing published few minutes
> >> ago. Seems people wants to focus docs first and release second (from 61
> >> votes).
> >> * In the other hand, I see Alex is still fighting with the release
> >> process.
> >> He stated that probably this week he will have the process ready to be
> >> tested by someone.
> >> If he get to that point that will be awesome, and hope others could be
> the
> >> first one in try to "push the button". If that works ok, we'll have a
> >> 0.9.6
> >> release (I think the one by Alex), and then a 0.9.7 (by that new release
> >> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay
> 1.0.
> >> For me release should happen at least from month to month. have sense?
> >>
> >> Just my my thoughts, but hope other want to share here what they can do
> >> and
> >> work to earn some money too! :)
> >>
> >>
> >>
> >> >
> >> > --
> >> > Carlos Rovira
> >> > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=g59S9iIx3J1aUO0NSJn6VaY%2Frn1KqfENiYYrz3kAzDI%3D&reserved=0>*
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7C223073f5986349c505e808d783dc894d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122855535324332&sdata=ASZFiHNLaimVkZYNcna1%2BgC99mX%2F%2Bs9lFcSQR43jh3A%3D&reserved=0
Re: Let's bump Royale version to 1.0
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Every day, I hope to hear news that Alina & Pashmina or Serkan or somebody else has deployed a production app using the MXRoyale and/or Spark Royale emulation components. But instead, I see more bugs being filed for "obvious" things. You can look at the issues list of open and fixed issues and the commits that fixed them to get a feel for it. Each of us has their own threshold of how good a 1.0 version should be, so if more of you can look at these bugs and think it is ok for a 1.0 to have these problems, then great, let's release the next version as 1.0, but when I try to remember what Flex 1.0 was like, I think it didn't have these kinds of problems.
As Carlos said below, we get one chance to make a good first impression, so I am being conservative. But it isn't my decision alone. It is really up to the rest of you.
-Alex
On 12/18/19, 6:41 AM, "Carlos Rovira" <ca...@apache.org> wrote:
Hi Piotr,
I'm afraid my perception is that we need to get to 1.0 in a natural way. I
mean: releasing 1.0 and giving exposure in all ways we can (webs, social
media, magazines,...), means people will try us. If they try and fail, will
never come back. So think about this as "only on bullet in your gun", if
you fail de shot, that will be bad for all the work we are done. I'm ok to
release 1.0 as soon as we see from "bird eye perspective" that all things
work as we expect.
For me that things are:
* Documentation will need to have at least some missing pages of features
like: DataBindnig, Loading External Data (HTTPSerice, RemoteObject, JSON),
View States, Item Renderers. Things like this are essential.
* Emulation components need to be in a shape that allow migrations in a
good degree. I think people approaching direct migration with emulation
components will many issues. I don't take into account look and feel of
emulation components, just functionality and working from a flex code
perspective, and just normal use cases with MX/Spark code, not third party
libraries that we have no control over. Simple apps like TDF, and examples
should work.
If we decided we want to bypass the previous, at least we need to ensure
"first try" of Royale for a newcomer (someone that knows very few about the
tech) is successful. This is most important things of all. The other two
are needed if we want people does not get frustrated and have solutions on
their own and stay with us. The opposite is people can have a first try
successful but abandon Royale due to unfinished things.
I think 0.9.7-SNAPSHOT captures in a realistic number where we are.
Technology works, and most people using it now can do lots of things, but
we still need to cover some things to reach that 1.0. We are not too far
but I think is still some month in the future.
just my 2 :)
Carlos
El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hello,
>
> This thread is old and this was the last message from me. What has changed
> on your end guys ?
>
> Thanks,
> Piotr
>
> wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Guys,
> >
> > Thank you so far for a great discussion. I see that there is an obvious
> > needs to improve documentation the most.
> >
> > I would like to express my personal feelings regarding releasing anything
> > what is not 1.0 after 0.9.6. Based on my experience with this project I
> > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less
> than
> > 6-8 months form now on. Even if we will have automatic release process I
> > cannot believe that is going to happen in a less time than I mention.
> >
> > Why I'm thinking like that:
> > - Justin just provided to the contributors generous offer - it's been
> > couple of days and there is absolutely no response.
> > - I've seen as part of the responses some concrete issues towards code in
> > SDK. I don't believe that there will be anyone who fix them UNLESS
> someone
> > need that stuff in his application which has been under development in
> his
> > daily job. Which leads me to conclusion that we will wait months before
> > anything from that list will be fixed.
> >
> > How Royale is going on right now?
> > In my original email I expressed that it is enough good to bump it to 1.0
> > - which gets us more credibility and push us to a better light. I got
> clear
> > responses from community that the only thing which is in the way of to
> 1.0
> > is documentation.
> >
> > W have one production app in Royale, another one has been created by
> > Carlos. I'm working on the third one. Justin mention fourth one which I'm
> > reviewing right now because it is written in Flex - it looks there won't
> be
> > problem with porting to Royale. To me it is enough proof that Royale is
> as
> > good as is to expose itself for more wider audience. Because this is
> > exactly what will happen when we bump to that magic 1.0.
> > People on this project are talking about community, my proposition to
> bump
> > Royale to 1.0 is towards community with hope that it helps grow thanks to
> > that step. With hope that finally I will see on the list more people,
> with
> > hope that I will see someone who doesn't have background in ActionScript,
> > but was curious about the project.
> >
> > In this thread I don't see rejection to my idea, so I'm going to work to
> > improve some areas and start release with bumped version to 1.0, whether
> it
> > will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is
> that
> > we are not facing in current version any walls during development, so
> this
> > is enough to me giving that framework 1.0.
> >
> > Thanks,
> > Piotr
> >
> > pon., 29 kwi 2019 o 19:44 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Hi Justin,
> >>
> >> great initiative, but some thoughts:
> >>
> >> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
> >> should we do. That's the apache way! :), only work towards the goal and
> >> giving advice to make things happen. We decisions are community managed
> >>
> >> 2.- I think is very generous offer so people can contribute and earn
> some
> >> money and a great plan,
> >>
> >> Some things you should take into account for the rewarding plan:
> >>
> >> * We just get results of the poll about releasing published few minutes
> >> ago. Seems people wants to focus docs first and release second (from 61
> >> votes).
> >> * In the other hand, I see Alex is still fighting with the release
> >> process.
> >> He stated that probably this week he will have the process ready to be
> >> tested by someone.
> >> If he get to that point that will be awesome, and hope others could be
> the
> >> first one in try to "push the button". If that works ok, we'll have a
> >> 0.9.6
> >> release (I think the one by Alex), and then a 0.9.7 (by that new release
> >> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay
> 1.0.
> >> For me release should happen at least from month to month. have sense?
> >>
> >> Just my my thoughts, but hope other want to share here what they can do
> >> and
> >> work to earn some money too! :)
> >>
> >>
> >>
> >> >
> >> > --
> >> > Carlos Rovira
> >> > https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ca12bdc4ec0104306acd108d783c84dab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122768633210188&sdata=ofAeMm0Ti2EWNadgqja1vEYf%2FR1X48mHt%2Fhl%2FOmuMhw%3D&reserved=0
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca12bdc4ec0104306acd108d783c84dab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122768633220182&sdata=M7hl9h%2BjYQYTQY9NZ20ItI3ePtwNckRp7BIHoDwHIO8%3D&reserved=0
> > <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca12bdc4ec0104306acd108d783c84dab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122768633220182&sdata=M7hl9h%2BjYQYTQY9NZ20ItI3ePtwNckRp7BIHoDwHIO8%3D&reserved=0>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca12bdc4ec0104306acd108d783c84dab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122768633220182&sdata=M7hl9h%2BjYQYTQY9NZ20ItI3ePtwNckRp7BIHoDwHIO8%3D&reserved=0
> <https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.patreon.com%2Fpiotrzarzycki&data=02%7C01%7Caharui%40adobe.com%7Ca12bdc4ec0104306acd108d783c84dab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122768633220182&sdata=M7hl9h%2BjYQYTQY9NZ20ItI3ePtwNckRp7BIHoDwHIO8%3D&reserved=0>*
>
--
Carlos Rovira
https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%2Fcarlosrovira&data=02%7C01%7Caharui%40adobe.com%7Ca12bdc4ec0104306acd108d783c84dab%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C637122768633220182&sdata=uPPSsfHrOG9eYwkJvReqNDXYPIS%2FK5tGtuTMMYzravk%3D&reserved=0
Re: Let's bump Royale version to 1.0
Posted by Carlos Rovira <ca...@apache.org>.
Hi Piotr,
I'm afraid my perception is that we need to get to 1.0 in a natural way. I
mean: releasing 1.0 and giving exposure in all ways we can (webs, social
media, magazines,...), means people will try us. If they try and fail, will
never come back. So think about this as "only on bullet in your gun", if
you fail de shot, that will be bad for all the work we are done. I'm ok to
release 1.0 as soon as we see from "bird eye perspective" that all things
work as we expect.
For me that things are:
* Documentation will need to have at least some missing pages of features
like: DataBindnig, Loading External Data (HTTPSerice, RemoteObject, JSON),
View States, Item Renderers. Things like this are essential.
* Emulation components need to be in a shape that allow migrations in a
good degree. I think people approaching direct migration with emulation
components will many issues. I don't take into account look and feel of
emulation components, just functionality and working from a flex code
perspective, and just normal use cases with MX/Spark code, not third party
libraries that we have no control over. Simple apps like TDF, and examples
should work.
If we decided we want to bypass the previous, at least we need to ensure
"first try" of Royale for a newcomer (someone that knows very few about the
tech) is successful. This is most important things of all. The other two
are needed if we want people does not get frustrated and have solutions on
their own and stay with us. The opposite is people can have a first try
successful but abandon Royale due to unfinished things.
I think 0.9.7-SNAPSHOT captures in a realistic number where we are.
Technology works, and most people using it now can do lots of things, but
we still need to cover some things to reach that 1.0. We are not too far
but I think is still some month in the future.
just my 2 :)
Carlos
El mié., 18 dic. 2019 a las 10:30, Piotr Zarzycki (<
piotrzarzycki21@gmail.com>) escribió:
> Hello,
>
> This thread is old and this was the last message from me. What has changed
> on your end guys ?
>
> Thanks,
> Piotr
>
> wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <pi...@gmail.com>
> napisał(a):
>
> > Hi Guys,
> >
> > Thank you so far for a great discussion. I see that there is an obvious
> > needs to improve documentation the most.
> >
> > I would like to express my personal feelings regarding releasing anything
> > what is not 1.0 after 0.9.6. Based on my experience with this project I
> > don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less
> than
> > 6-8 months form now on. Even if we will have automatic release process I
> > cannot believe that is going to happen in a less time than I mention.
> >
> > Why I'm thinking like that:
> > - Justin just provided to the contributors generous offer - it's been
> > couple of days and there is absolutely no response.
> > - I've seen as part of the responses some concrete issues towards code in
> > SDK. I don't believe that there will be anyone who fix them UNLESS
> someone
> > need that stuff in his application which has been under development in
> his
> > daily job. Which leads me to conclusion that we will wait months before
> > anything from that list will be fixed.
> >
> > How Royale is going on right now?
> > In my original email I expressed that it is enough good to bump it to 1.0
> > - which gets us more credibility and push us to a better light. I got
> clear
> > responses from community that the only thing which is in the way of to
> 1.0
> > is documentation.
> >
> > W have one production app in Royale, another one has been created by
> > Carlos. I'm working on the third one. Justin mention fourth one which I'm
> > reviewing right now because it is written in Flex - it looks there won't
> be
> > problem with porting to Royale. To me it is enough proof that Royale is
> as
> > good as is to expose itself for more wider audience. Because this is
> > exactly what will happen when we bump to that magic 1.0.
> > People on this project are talking about community, my proposition to
> bump
> > Royale to 1.0 is towards community with hope that it helps grow thanks to
> > that step. With hope that finally I will see on the list more people,
> with
> > hope that I will see someone who doesn't have background in ActionScript,
> > but was curious about the project.
> >
> > In this thread I don't see rejection to my idea, so I'm going to work to
> > improve some areas and start release with bumped version to 1.0, whether
> it
> > will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is
> that
> > we are not facing in current version any walls during development, so
> this
> > is enough to me giving that framework 1.0.
> >
> > Thanks,
> > Piotr
> >
> > pon., 29 kwi 2019 o 19:44 Carlos Rovira <ca...@apache.org>
> > napisał(a):
> >
> >> Hi Justin,
> >>
> >> great initiative, but some thoughts:
> >>
> >> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
> >> should we do. That's the apache way! :), only work towards the goal and
> >> giving advice to make things happen. We decisions are community managed
> >>
> >> 2.- I think is very generous offer so people can contribute and earn
> some
> >> money and a great plan,
> >>
> >> Some things you should take into account for the rewarding plan:
> >>
> >> * We just get results of the poll about releasing published few minutes
> >> ago. Seems people wants to focus docs first and release second (from 61
> >> votes).
> >> * In the other hand, I see Alex is still fighting with the release
> >> process.
> >> He stated that probably this week he will have the process ready to be
> >> tested by someone.
> >> If he get to that point that will be awesome, and hope others could be
> the
> >> first one in try to "push the button". If that works ok, we'll have a
> >> 0.9.6
> >> release (I think the one by Alex), and then a 0.9.7 (by that new release
> >> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay
> 1.0.
> >> For me release should happen at least from month to month. have sense?
> >>
> >> Just my my thoughts, but hope other want to share here what they can do
> >> and
> >> work to earn some money too! :)
> >>
> >>
> >>
> >> >
> >> > --
> >> > Carlos Rovira
> >> > http://about.me/carlosrovira
> >> >
> >> >
> >> >
> >> >
> >>
> >
> >
> > --
> >
> > Piotr Zarzycki
> >
> > Patreon: *https://www.patreon.com/piotrzarzycki
> > <https://www.patreon.com/piotrzarzycki>*
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Carlos Rovira
http://about.me/carlosrovira
Re: Let's bump Royale version to 1.0
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hello,
This thread is old and this was the last message from me. What has changed
on your end guys ?
Thanks,
Piotr
wt., 30 kwi 2019 o 10:07 Piotr Zarzycki <pi...@gmail.com>
napisał(a):
> Hi Guys,
>
> Thank you so far for a great discussion. I see that there is an obvious
> needs to improve documentation the most.
>
> I would like to express my personal feelings regarding releasing anything
> what is not 1.0 after 0.9.6. Based on my experience with this project I
> don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less than
> 6-8 months form now on. Even if we will have automatic release process I
> cannot believe that is going to happen in a less time than I mention.
>
> Why I'm thinking like that:
> - Justin just provided to the contributors generous offer - it's been
> couple of days and there is absolutely no response.
> - I've seen as part of the responses some concrete issues towards code in
> SDK. I don't believe that there will be anyone who fix them UNLESS someone
> need that stuff in his application which has been under development in his
> daily job. Which leads me to conclusion that we will wait months before
> anything from that list will be fixed.
>
> How Royale is going on right now?
> In my original email I expressed that it is enough good to bump it to 1.0
> - which gets us more credibility and push us to a better light. I got clear
> responses from community that the only thing which is in the way of to 1.0
> is documentation.
>
> W have one production app in Royale, another one has been created by
> Carlos. I'm working on the third one. Justin mention fourth one which I'm
> reviewing right now because it is written in Flex - it looks there won't be
> problem with porting to Royale. To me it is enough proof that Royale is as
> good as is to expose itself for more wider audience. Because this is
> exactly what will happen when we bump to that magic 1.0.
> People on this project are talking about community, my proposition to bump
> Royale to 1.0 is towards community with hope that it helps grow thanks to
> that step. With hope that finally I will see on the list more people, with
> hope that I will see someone who doesn't have background in ActionScript,
> but was curious about the project.
>
> In this thread I don't see rejection to my idea, so I'm going to work to
> improve some areas and start release with bumped version to 1.0, whether it
> will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is that
> we are not facing in current version any walls during development, so this
> is enough to me giving that framework 1.0.
>
> Thanks,
> Piotr
>
> pon., 29 kwi 2019 o 19:44 Carlos Rovira <ca...@apache.org>
> napisał(a):
>
>> Hi Justin,
>>
>> great initiative, but some thoughts:
>>
>> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
>> should we do. That's the apache way! :), only work towards the goal and
>> giving advice to make things happen. We decisions are community managed
>>
>> 2.- I think is very generous offer so people can contribute and earn some
>> money and a great plan,
>>
>> Some things you should take into account for the rewarding plan:
>>
>> * We just get results of the poll about releasing published few minutes
>> ago. Seems people wants to focus docs first and release second (from 61
>> votes).
>> * In the other hand, I see Alex is still fighting with the release
>> process.
>> He stated that probably this week he will have the process ready to be
>> tested by someone.
>> If he get to that point that will be awesome, and hope others could be the
>> first one in try to "push the button". If that works ok, we'll have a
>> 0.9.6
>> release (I think the one by Alex), and then a 0.9.7 (by that new release
>> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay 1.0.
>> For me release should happen at least from month to month. have sense?
>>
>> Just my my thoughts, but hope other want to share here what they can do
>> and
>> work to earn some money too! :)
>>
>>
>>
>> >
>> > --
>> > Carlos Rovira
>> > http://about.me/carlosrovira
>> >
>> >
>> >
>> >
>>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Let's bump Royale version to 1.0
Posted by Piotr Zarzycki <pi...@gmail.com>.
Hi Guys,
Thank you so far for a great discussion. I see that there is an obvious
needs to improve documentation the most.
I would like to express my personal feelings regarding releasing anything
what is not 1.0 after 0.9.6. Based on my experience with this project I
don't believe that releasing 0.9.7, 0.9.8 till 1.0 etc. will take less than
6-8 months form now on. Even if we will have automatic release process I
cannot believe that is going to happen in a less time than I mention.
Why I'm thinking like that:
- Justin just provided to the contributors generous offer - it's been
couple of days and there is absolutely no response.
- I've seen as part of the responses some concrete issues towards code in
SDK. I don't believe that there will be anyone who fix them UNLESS someone
need that stuff in his application which has been under development in his
daily job. Which leads me to conclusion that we will wait months before
anything from that list will be fixed.
How Royale is going on right now?
In my original email I expressed that it is enough good to bump it to 1.0 -
which gets us more credibility and push us to a better light. I got clear
responses from community that the only thing which is in the way of to 1.0
is documentation.
W have one production app in Royale, another one has been created by
Carlos. I'm working on the third one. Justin mention fourth one which I'm
reviewing right now because it is written in Flex - it looks there won't be
problem with porting to Royale. To me it is enough proof that Royale is as
good as is to expose itself for more wider audience. Because this is
exactly what will happen when we bump to that magic 1.0.
People on this project are talking about community, my proposition to bump
Royale to 1.0 is towards community with hope that it helps grow thanks to
that step. With hope that finally I will see on the list more people, with
hope that I will see someone who doesn't have background in ActionScript,
but was curious about the project.
In this thread I don't see rejection to my idea, so I'm going to work to
improve some areas and start release with bumped version to 1.0, whether it
will be after 0.9.7, 0.9.8 it doesn't matter - What's really matter is that
we are not facing in current version any walls during development, so this
is enough to me giving that framework 1.0.
Thanks,
Piotr
pon., 29 kwi 2019 o 19:44 Carlos Rovira <ca...@apache.org>
napisał(a):
> Hi Justin,
>
> great initiative, but some thoughts:
>
> 1.- As Olaf said, Alex or I are just two more devs, so we can say what
> should we do. That's the apache way! :), only work towards the goal and
> giving advice to make things happen. We decisions are community managed
>
> 2.- I think is very generous offer so people can contribute and earn some
> money and a great plan,
>
> Some things you should take into account for the rewarding plan:
>
> * We just get results of the poll about releasing published few minutes
> ago. Seems people wants to focus docs first and release second (from 61
> votes).
> * In the other hand, I see Alex is still fighting with the release process.
> He stated that probably this week he will have the process ready to be
> tested by someone.
> If he get to that point that will be awesome, and hope others could be the
> first one in try to "push the button". If that works ok, we'll have a 0.9.6
> release (I think the one by Alex), and then a 0.9.7 (by that new release
> manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay 1.0.
> For me release should happen at least from month to month. have sense?
>
> Just my my thoughts, but hope other want to share here what they can do and
> work to earn some money too! :)
>
>
>
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
> >
> >
> >
> >
>
--
Piotr Zarzycki
Patreon: *https://www.patreon.com/piotrzarzycki
<https://www.patreon.com/piotrzarzycki>*
Re: Let's bump Royale version to 1.0 -- submit your bid for
assistance to the group by Friday May 3
Posted by Carlos Rovira <ca...@apache.org>.
Hi Justin,
great initiative, but some thoughts:
1.- As Olaf said, Alex or I are just two more devs, so we can say what
should we do. That's the apache way! :), only work towards the goal and
giving advice to make things happen. We decisions are community managed
2.- I think is very generous offer so people can contribute and earn some
money and a great plan,
Some things you should take into account for the rewarding plan:
* We just get results of the poll about releasing published few minutes
ago. Seems people wants to focus docs first and release second (from 61
votes).
* In the other hand, I see Alex is still fighting with the release process.
He stated that probably this week he will have the process ready to be
tested by someone.
If he get to that point that will be awesome, and hope others could be the
first one in try to "push the button". If that works ok, we'll have a 0.9.6
release (I think the one by Alex), and then a 0.9.7 (by that new release
manager). At that point, I figure we can plan 0.9.8, 0.9.9 and Finlay 1.0.
For me release should happen at least from month to month. have sense?
Just my my thoughts, but hope other want to share here what they can do and
work to earn some money too! :)
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>
Re: Let's bump Royale version to 1.0 -- submit your bid for
assistance to the group by Friday May 3
Posted by Olaf Krueger <ma...@olafkrueger.net>.
Hi Justin,
thanks for your amazing offer!
> ...what Alex and Carlos want to see happen...
Before others will do this I would just like to mention that no individuals
make decisions here at Apache. It's always the community! ;-)
However, I am curious about the feedback!
Thanks,
Olaf
--
Sent from: http://apache-royale-development.20373.n8.nabble.com/
Re: Let's bump Royale version to 1.0 -- submit your bid for
assistance to the group by Friday May 3
Posted by Carlos Rovira <ca...@apache.org>.
Hi Dany,
El mar., 30 abr. 2019 a las 5:55, Dany Dhondt (<ar...@mac.com.invalid>)
escribió:
> Hi Justin,
>
> As much as I would like to write an article on Royale vs. competitors, I
> can’t do so at this moment because I don’t have enough Royale knowledge
> yet. But there are things I could point at so that the Royale team can
> formulate answers.
> Here are some questions and ideas I have which could be addressed:
>
> 1. Royale blog
> On our site, there is a section called ‘blog’. Shouldn’t we rename that?
> To me, a blog is something of the past. ‘Examples’ or ‘Code snippets’ or
> something similar would be better.
>
I'm ok with this, but we must get the right word. Currently we use "blog"
for:
* announcements and notify releases
* articles
* examples (ala Peter Dehaan's flex blog examples style)
So "Examples" is not right to me since we are posting announcements, while
articles could be a more elaborated writing about some concept that could
have examples.
I'm ok to change it if others want if we found a label more generic and
modern
>
> 2. Faq
> We definitely need a faq. Common answers to basic questions can go there.
> Also, when our StackOverflow database gets rolling, we can put links to our
> faq there.
>
Yeah! I thought on this too. This could be a good point to work on. There's
already a page (link on footer), with some points a put when created the
page.
Making a good FAQ page would be great. And there's many things and sections
we can add to it. This maybe could be a good point for you to start if you
want
>
> 3. (Re)rendering
> One of the core principles of React is that it uses a virtual dom. You
> never write to the dom directly. React does that for you. That’s why JQuery
> doesn’t match at all with React. The main advantage of this, is that only
> those DOM nodes get updated which actually change, making React really
> fast. How does Royale tackle this? Can someone explain this in an easy to
> understand way?
>
I think Harbs explained this, but maybe we should have a more compressive
data about this. Maybe if Harbs is very busy right now Alex could give us a
paragraph or something about this.
For what I understand Royale is more fast than React, but don't have the
proper words or concepts ready to explain this in a more technical way.
> 4. Managing (global) state
> Updating a component in React is done by calling setState() and passing an
> object to that method. That’s all very well and simple in small projects.
> Passing state from parents to children is straightforward. You just pass
> in state as props to underlying components. The other way around though is
> hard, very hard. Handling global state is done by implementing 3rd party
> technologies like Redux, MobX or recently by implementing React hooks.
> I believe that Royale binding mechanisms could be superior to this. So the
> question here: how does Royale handles global sta
>
I think you refer here how to deal with global models in apps in opposite
to models of single components.
In flex we had frameworks like Swiz, Parsley and more.
In Royale PureMVC is already working, although for example I'm not using it
in out real app yet. But I think this is what you have right now to use as
today.
We plan to make a new library based on metadata to mimic the most important
functionality that we had in Swiz, I refer to [Dispatcher],
[EventDispatcher] and [Inject]
This is a requisite for our next real app iteration, but still can say when
will start to wok on that, only can say that hopefully will be soon and
will be donated to Apache Royale
>
> 5. Justin, at some point in your message, you talk about ‘command line
> nonsense’. I believe you’re right and wrong at the same time.
> Right because indeed, learning React is far more than learning one
> technology. You have to dig through npm, node, JSX, typescript (if you want
> strong typing), webpack/rollup, babel, … and in the end, most of us use
> create-react-app just to hide all those configurations. BUT
> Wrong because there is a massive open source community where you can find
> almost anything you might need in your project. Building a modern web app
> is all about combining existing code to create your application.
> That brings me to this question: is it possible to embed existing pure
> javascript components into Royale?
>
yes! I think I need to make soon a blog example about this. For example in
Tour de Jewel, the code coloring is done by another JS script calling its
methods. Other way is wrapping in Royale classes like we did with Material
Design Lite (MDL UI set). I think there's more with typedefs, but I need to
learn more from this. I'll ask Alex/Harbs to explain more about this.
> An example: one of the most crucial components in any admin application is
> a calendar. In my Flex days, I had to spend hundreds of dollars to get a
> decent calendar component. In React, I use fullcalendar which is a great
> calendar/sheduling javascript component. Creating a calendar component from
> scratch takes years as anyone who has tried will confirm.
>
Yeah, it took some work to get Jewel DateChooser fully working, and a
Calendar component done in Royale will be work. Maybe is better to use
other third party one for now. But in the end we should try to create our
own versions that will grow with time.
> 6. Components, components, components, …
> As I stated before, embracing a new application technology involves the
> immediate availability of standard components. PAYG architecture, beads and
> strands is all very powerful, but as a developer new to Royale, I’d want
> ready-to-use, powerful, beautiful components which interoperate seamlessly.
>
Yes, Jewel tries to create components that could be easily be visual
customized, with themes mainly and by CSS in the specific case. So we need
to work more on the official Jewel themself and create some more that shows
how different it could be from one to another just by creating your own
styles, and in the other hand we should create more Jewel components that
tries to bring all possibilities, and incorporate to Royale Jewel library
or make other expansion libraries...
>
> Just some random thoughts…
>
>
> Dany
>
> --
> Carlos Rovira
> http://about.me/carlosrovira
>
>
>
>
Re: Let's bump Royale version to 1.0 -- submit your bid for
assistance to the group by Friday May 3
Posted by Dany Dhondt <ar...@mac.com.INVALID>.
Hi Justin,
As much as I would like to write an article on Royale vs. competitors, I can’t do so at this moment because I don’t have enough Royale knowledge yet. But there are things I could point at so that the Royale team can formulate answers.
Here are some questions and ideas I have which could be addressed:
1. Royale blog
On our site, there is a section called ‘blog’. Shouldn’t we rename that? To me, a blog is something of the past. ‘Examples’ or ‘Code snippets’ or something similar would be better.
2. Faq
We definitely need a faq. Common answers to basic questions can go there. Also, when our StackOverflow database gets rolling, we can put links to our faq there.
3. (Re)rendering
One of the core principles of React is that it uses a virtual dom. You never write to the dom directly. React does that for you. That’s why JQuery doesn’t match at all with React. The main advantage of this, is that only those DOM nodes get updated which actually change, making React really fast. How does Royale tackle this? Can someone explain this in an easy to understand way?
4. Managing (global) state
Updating a component in React is done by calling setState() and passing an object to that method. That’s all very well and simple in small projects.
Passing state from parents to children is straightforward. You just pass in state as props to underlying components. The other way around though is hard, very hard. Handling global state is done by implementing 3rd party technologies like Redux, MobX or recently by implementing React hooks.
I believe that Royale binding mechanisms could be superior to this. So the question here: how does Royale handles global state?
5. Justin, at some point in your message, you talk about ‘command line nonsense’. I believe you’re right and wrong at the same time.
Right because indeed, learning React is far more than learning one technology. You have to dig through npm, node, JSX, typescript (if you want strong typing), webpack/rollup, babel, … and in the end, most of us use create-react-app just to hide all those configurations. BUT
Wrong because there is a massive open source community where you can find almost anything you might need in your project. Building a modern web app is all about combining existing code to create your application.
That brings me to this question: is it possible to embed existing pure javascript components into Royale?
An example: one of the most crucial components in any admin application is a calendar. In my Flex days, I had to spend hundreds of dollars to get a decent calendar component. In React, I use fullcalendar which is a great calendar/sheduling javascript component. Creating a calendar component from scratch takes years as anyone who has tried will confirm.
6. Components, components, components, …
As I stated before, embracing a new application technology involves the immediate availability of standard components. PAYG architecture, beads and strands is all very powerful, but as a developer new to Royale, I’d want ready-to-use, powerful, beautiful components which interoperate seamlessly.
Just some random thoughts…
Dany
> Op 27 apr. 2019, om 06:52 heeft Justin M. Hill <Ju...@prominic.net> het volgende geschreven:
>
> Hi Dany,
>
> Are you willing to write an article about why users should choose or at least consider heavily Apache Royale over the competitors - React, Vue, and Angular?
>
> I think it is important to clearly explain "Why you should care about Royale" on the homepage compared to the competitors you mentioned.
>
> Ideally, this article would be written not just for those with an ActionScript or Flex code base that are seeking a modernization target.
>
>
>
> The Moonshine IDE team is willing to donate $2,500 USD in total over the next 30 days to anyone who can accomplish what Alex and Carlos want to see happen to call it release 1.0.
>
> IF you who are willing to step up to the plate immediately (with a deliverable no later than May 26, 2019) to help with:
>
> * documentation (ASDoc style)
>
> * examples (code snippets that do things like Tour de Royale)
>
> * tutorials (well written, friendly, understandable, educational material)
>
> * a mini reproduction of the aforementioned Flex In a Week Series (great idea!)
> https://www.adobe.com/devnet/flex/videotraining.html <https://www.adobe.com/devnet/flex/videotraining.html>
>
> * build automation
>
> * automated test cases
>
> * creation of a summary comparison table showing Royale relative to React, Vue, Angular
>
> * a longer write up of competitive articles detailed why Royale is important. BTW, one reason it can be important is because it is NOT controlled by giant companies.
>
> * a directory of consultants for hire:
>
> * OR anything else Alex and Carlos specifically need to be convinced to push to 1.0 release
>
> THEN
>
> Please submit to this public group your commitment and cost.
>
> We will then do this democratically:
> deadline for bid submissions is 7 days from now -- Friday May 3.
> Carlos (or someone who knows Twitter enough to create another poll) will then do another Twitter vote poll for 3 days to decide who gets the bids
>
>
>
> Ideally multiple people will commit to doing something "small" for $500 each and we can award 5 people the projects.
>
> The $2,500 USD total will be paid via PayPal. No exceptions.
>
>
> IF within 30 days Apache Royale 1.0 is released to the public then the Moonshine IDE team will again donate $2,500 for the month of June in an identical voting scenario (assuming this one works well) to bring home a 1.1 release.
>
>
> By 60 days from now, a new user who has never seen Royale before or programmed in ActionScript should be able to:
> 1) Arrive at the Apache Royale web page
>
> 2) Understand from the home page why they should care about the project if they come from React, Vue, Angular, Flex, or ActionScript worlds
>
> 3) Be able to within 5 mouse clicks (download button, install button, launch button, build button, run button) go from having nothing on their machine to having an IDE (we of course volunteer Moonshine but Visual Studio Code should be a goal for this, too) on their machine with a successful build of their first "hello world". No command line nonsense. No learning NPM, Git, downloading 20 required packages. See Royale website. Want to try it. 5 clicks later build your Hello World.
>
> If the above 3 goals are met, then the Moonshine IDE team will run a 3rd donation round of $2,500 for the month of July in a manner to the description above to bring home a 1.2 release, to be published no later than the end of July 2019 for the awards to be paid.
>
>
> Hopefully this helps motivate the team.
>
> Thank you,
>
> Justin Hill
>
>
>
>
> dev-digest-help---04/26/2019 11:04:17 PM---dev Digest 27 Apr 2019 04:04:13 -0000 Issue 1966 Topics (messages 9894 through 9902)
>
> From: dev-digest-help@royale.apache.org
> To: dev@royale.apache.org
> Date: 04/26/2019 11:04 PM
> Subject: [External] dev Digest 27 Apr 2019 04:04:13 -0000 Issue 1966 - Dany replies about React, Vue, Angular
>
>
>
>
> dev Digest 27 Apr 2019 04:04:13 -0000 Issue 1966
>
> Topics (messages 9894 through 9902)
>
> Re: Let's bump Royale version to 1.0
> 9894 by: Dany Dhondt
> 9896 by: Carlos Rovira
>
> Re: Version property (was: Let's bump Royale version to 1.0)
> 9895 by: Alex Harui
>
> Release Step 001 Succeeded
> 9897 by: Apache Royale CI Server
>
> Release Step 001a Succeeded
> 9898 by: Apache Royale CI Server
>
> Release Step 002 Succeeded
> 9899 by: Apache Royale CI Server
>
> Release Step 002a Succeeded
> 9900 by: Apache Royale CI Server
>
> Release Step 003 Succeeded
> 9901 by: Apache Royale CI Server
>
> Build failed in Jenkins: royale-asjs_MXTests #722
> 9902 by: Apache Royale CI Server
>
> Administrivia:
>
> ---------------------------------------------------------------------
> To post to the list, e-mail: dev@royale.apache.org
> To unsubscribe, e-mail: dev-digest-unsubscribe@royale.apache.org
> For additional commands, e-mail: dev-digest-help@royale.apache.org
>
> ----------------------------------------------------------------------
>
>
> ----- Message from Dany Dhondt <ar...@mac.com.INVALID> on Fri, 26 Apr 2019 16:06:59 +0200 -----
> To:
> dev@royale.apache.org
> Subject:
> Re: Let's bump Royale version to 1.0
> I’m all for buikding a knowledge base in Stack Overflow! The mailing list should only be used for developing Royale. Questions about using Royale should go to SO
>
> The competitors of Royale are React, Vue, Angular, ...
> Lots of developers are now used to those workflows.
> In case of React, create-react-app sets you up with a brand new, ready to go project in less than 30 seconds. That should be a benchmark for Royale imo.
>
> Dany
>
>
> Verstuurd vanaf mijn iPhone
>
> > Op 26 apr. 2019 om 12:42 heeft Frost, Andrew <An...@harman.com> het volgende geschreven:
> >
> > One other thought ... currently the way people ask for support is via these mailing lists. Which are okay but I'm always conscious that I'm potentially spamming people, plus the volume of mails is such that I have a rule to push all these into a folder that I then review every day or two..
> >
> > But if I want to find something out, I tend not to go search the mailing list, I tend to search online. Looking through mailing list threads isn't the easiest (and search engines don't necessarily pick things up from them very well) but a major source of support is Stack Overflow... I use this a lot with my other work and there's a lot of information there.
> >
> > Apache Royale doesn't appear to have a tag; when I search for "royale" all I got was stuff about "Clash Royale"; there are however 8 questions with "flexjs" tags.
> >
> > But wouldn't it be good for people to add questions and to contribute answers there, both from the user perspective and perhaps also the dev perspective? Would be interested in people's thoughts... (and perhaps I'll have to dig out my SO credentials to start contributing there....)
> >
> > thanks
> >
> > Andrew
> >
> >
> > -----Original Message-----
> > From: Carlos Rovira [mailto:carlosrovira@apache.org <ma...@apache.org>]
> > Sent: 26 April 2019 10:39
> > To: dev@royale.apache.org
> > Subject: [EXTERNAL] Re: Let's bump Royale version to 1.0
> >
> > Hi Angelo, that's great! :)
> >
> > any help here is very appreciated.
> >
> > Share in a new mail a concrete contribution before starting to work on it, so we can know about it and help you on the task so your work fit perfectly in the overall picture.
> >
> > I'd like to create videos too, and people asked about it in facebook and twitter. Do you have skills in creating videos?
> >
> >
> >
> > El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<la...@gmail.com>)
> > escribió:
> >
> >> Yes, i can give some slots to help with documentation or example
> >> project or so... I think tutorial videos could be help to understand
> >> rapidly the platform and could help new user to get ready in a few
> >> hours to start build their project.
> >>
> >> Angelo
> >>
> >> On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira
> >> <ca...@apache.org>
> >> wrote:
> >>
> >>> Agree with latest comments.
> >>>
> >>> I think we should work in docs and ease the start of new users to
> >>> target
> >>> 1.0
> >>> And in the process fix some few things (i.e: don't want to reach 1.0
> >>> with Jewel Table in its current state and API)
> >>>
> >>> What do you think?
> >>>
> >>> If you all agree could you think on how to contribute to that
> >>> effort? Can we have as a near goal to bring 1.0 planing ourselves to
> >>> donate some
> >> hours
> >>> to Apache Royale to make this happen? If some of us help in the
> >>> current state I think we can get to it sooner.
> >>>
> >>> Thanks
> >>>
> >>>
> >>> El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> >>> lazzari.angelo@gmail.com>)
> >>> escribió:
> >>>
> >>>> I am completely agree with Olaf: start using a new platform where
> >>>> the documentation is not complete, clean and updated it is a
> >>>> really bad thing...and it would be a potential reason to increase
> >>>> the difficulty
> >> to
> >>>> adopt the platform...
> >>>>
> >>>> Angelo
> >>>>
> >>>> El vie., 26 abr. 2019 8:54, Olaf Krueger <ma...@olafkrueger.net>
> >>> escribió:
> >>>>
> >>>>> Hi,
> >>>>>
> >>>>> Basically, I think it's important to provide a great developer
> >>>> experience.
> >>>>> IMO, that's more important than trying to implement missing features.
> >>>>>
> >>>>> One thing to achieve this is documentation of course.
> >>>>> Thanks to all of you there already exist a lot of docs, but it
> >>>>> feels
> >> a
> >>>> bit
> >>>>> messy because they are hosted at different places, e.g.:
> >>>>>
> >>>>> - royale-docs repo
> >>>>> - royale-asjs wiki
> >>>>> - royale-asjs Readme
> >>>>> -
> >>>>> https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http <https://clicktime.symantec.com/3SEvxFs2HbjNAgsLBEtNLr17Vc?u=http>
> >>>>> s%3A%2F%2Froyale.apache.org
> >>>>> - ...?
> >>>>>
> >>>>> As a user, it's hard to get an overview of what is available...
> >>>>> and
> >>>> where.
> >>>>> Maybe it's a good idea to consolidate the docs before releasing 1.0.
> >>>>>
> >>>>> Just my 2 cents,
> >>>>> Olaf
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Sent from:
> >>>>> https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http <https://clicktime.symantec.com/3LM5ngUtumonkv3VTyrZRJ77Vc?u=http>
> >>>>> %3A%2F%2Fapache-royale-development.20373.n8.nabble.com%2F
> >>>>>
> >>>>
> >>>
> >>>
> >>> --
> >>> Carlos Rovira
> >>> https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A% <https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%>
> >>> 2F%2Fabout.me%2Fcarlosrovira
> >>>
> >>
> >>
> >> --
> >> Angelo Lazzari
> >> mobile: +34 683 137 087
> >> mail: lazzari.angelo@gmail.com
> >>
> >>
> >>
> >> ----------------------------------------------------------------------
> >> --------------------------------------------------
> >> Verify the correspondence of the addressee; otherwise, notify that to
> >> the sender and, conscious of the responsibility for the undue use,
> >> destroy the message and its copies.
> >>
> >> ----------------------------------------------------------------------
> >> --------------------------------------------------
> >>
> >
> >
> > --
> > Carlos Rovira
> > https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira <https://clicktime.symantec.com/38jVp7aJ4ouZou8k1qd97Hn7Vc?u=http%3A%2F%2Fabout.me%2Fcarlosrovira>
>
>
>
> ----- Message from Carlos Rovira <ca...@apache.org> on Fri, 26 Apr 2019 20:45:32 +0200 -----
> To:
> dev@royale.apache.org
> Subject:
> Re: Let's bump Royale version to 1.0
> That's great Angelo! :)
>
> El vie., 26 abr. 2019 a las 13:06, Angelo Lazzari (<la...@gmail.com>)
> escribió:
>
> > yes, I always send video to my client, it is a really good way to explain
> > new process and teach things...
> >
> > I will write a new email about the video course...
> >
> > Angelo
> >
> > On Fri, Apr 26, 2019 at 11:39 AM Carlos Rovira <ca...@apache.org>
> > wrote:
> >
> > > Hi Angelo, that's great! :)
> > >
> > > any help here is very appreciated.
> > >
> > > Share in a new mail a concrete contribution before starting to work on
> > it,
> > > so we can know about it and help you on the task so your work fit
> > perfectly
> > > in the overall picture.
> > >
> > > I'd like to create videos too, and people asked about it in facebook and
> > > twitter. Do you have skills in creating videos?
> > >
> > >
> > >
> > > El vie., 26 abr. 2019 a las 10:47, Angelo Lazzari (<
> > > lazzari.angelo@gmail.com>)
> > > escribió:
> > >
> > > > Yes, i can give some slots to help with documentation or example
> > project
> > > or
> > > > so... I think tutorial videos could be help to understand rapidly the
> > > > platform and could help new user to get ready in a few hours to start
> > > build
> > > > their project.
> > > >
> > > > Angelo
> > > >
> > > > On Fri, Apr 26, 2019 at 10:42 AM Carlos Rovira <
> > carlosrovira@apache.org>
> > > > wrote:
> > > >
> > > > > Agree with latest comments.
> > > > >
> > > > > I think we should work in docs and ease the start of new users to
> > > target
> > > > > 1.0
> > > > > And in the process fix some few things (i.e: don't want to reach 1.0
> > > with
> > > > > Jewel Table in its current state and API)
> > > > >
> > > > > What do you think?
> > > > >
> > > > > If you all agree could you think on how to contribute to that effort?
> > > Can
> > > > > we have as a near goal to bring 1.0 planing ourselves to donate some
> > > > hours
> > > > > to Apache Royale to make this happen? If some of us help in the
> > current
> > > > > state I think we can get to it sooner.
> > > > >
> > > > > Thanks
> > > > >
> > > > >
> > > > > El vie., 26 abr. 2019 a las 9:57, Angelo Lazzari (<
> > > > > lazzari.angelo@gmail.com>)
> > > > > escribió:
> > > > >
> > > > > > I am completely agree with Olaf: start using a new platform where
> > the
> > > > > > documentation is not complete, clean and updated it is a really bad
> > > > > > thing...and it would be a potential reason to increase the
> > difficulty
> > > > to
> > > > > > adopt the platform...
> > > > > >
> > > > > > Angelo
> > > > > >
> > > > > > El vie., 26 abr. 2019 8:54, Olaf Krueger <ma...@olafkrueger.net>
> > > > > escribió:
> > > > > >
> > > > > > > Hi,
> > > > > > >
> > > > > > > Basically, I think it's important to provide a great developer
> > > > > > experience.
> > > > > > > IMO, that's more important than trying to implement missing
> > > features.
> > > > > > >
> > > > > > > One thing to achieve this is documentation of course.
> > > > > > > Thanks to all of you there already exist a lot of docs, but it
> > > feels
> > > > a
> > > > > > bit
> > > > > > > messy because they are hosted at different places, e.g.:
> > > > > > >
> > > > > > > - royale-docs repo
> > > > > > > - royale-asjs wiki
> > > > > > > - royale-asjs Readme
> > > > > > > - https://royale.apache.org <https://royale.apache.org/>
> > > > > > > - ...?
> > > > > > >
> > > > > > > As a user, it's hard to get an overview of what is available...
> > and
> > > > > > where.
> > > > > > > Maybe it's a good idea to consolidate the docs before releasing
> > > 1.0.
> > > > > > >
> > > > > > > Just my 2 cents,
> > > > > > > Olaf
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Sent from: http://apache-royale-development.20373.n8.nabble.com/ <http://apache-royale-development.20373.n8.nabble.com/>
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Carlos Rovira
> > > > > http://about.me/carlosrovira <http://about.me/carlosrovira>
> > > > >
> > > >
> > > >
> > > > --
> > > > Angelo Lazzari
> > > > mobile: +34 683 137 087
> > > > mail: lazzari.angelo@gmail.com
> > > >
> > > >
> > > >
> > > >
> > >
> > ------------------------------------------------------------------------------------------------------------------------
> > > > Verify the correspondence of the addressee; otherwise, notify that to
> > the
> > > > sender and, conscious of the responsibility for the undue use, destroy
> > > the
> > > > message and its copies.
> > > >
> > > >
> > >
> > ------------------------------------------------------------------------------------------------------------------------
> > > >
> > >
> > >
> > > --
> > > Carlos Rovira
> > > http://about.me/carlosrovira <http://about.me/carlosrovira>
> > >
> >
> >
> > --
> > Angelo Lazzari
> > mobile: +34 683 137 087
> > mail: lazzari.angelo@gmail.com
> >
> >
> >
> > ------------------------------------------------------------------------------------------------------------------------
> > Verify the correspondence of the addressee; otherwise, notify that to the
> > sender and, conscious of the responsibility for the undue use, destroy the
> > message and its copies.
> >
> > ------------------------------------------------------------------------------------------------------------------------
> >
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira <http://about.me/carlosrovira>
>
> ----- Message from Alex Harui <ah...@adobe.com.INVALID> on Fri, 26 Apr 2019 16:02:19 +0000 -----
> To:
> "dev@royale.apache.org" <de...@royale.apache.org>
> Subject:
> Re: Version property (was: Let's bump Royale version to 1.0)
>
>
> On 4/26/19, 4:29 AM, "Kessler CTR Mark J" <ma...@usmc.mil.INVALID> wrote:
>
> > So far, we have not had the release scripts properly generate the right version number for the NPM artifacts.
>
>
> This spurred a question for me. Is there a way to find out what version number the SDK binaries are in code for Royale? Sort of like the Flex SDK mx.core.FlexVersion or at least a build date?
>
> Not at this time. IMO, runtime versioning wasn't worth the cost of all of those strings and code in the production app. Also, Royale was designed from the beginning to try to be "version-agnostic". By using loose-coupling via Beads/PAYG/ValuesManager and lots of interfaces instead of direct class references, there shouldn't be a need to deal with version incompatibilities at runtime like Flex did with the Marshall Plan and FlexVersion and more.
>
> Flex had to care about version incompatibilities because the fundamental base classes were not loosely-coupled. Flex HelloWorld was 128K not just because UIComponent was huge, but because UIComponent pulled in other classes as init-time strongly-coupled dependencies. A good thing to think about as you write Royale framework code is, "can every dependency be easily replaced"?
>
> After we hit 1.0 (and hopefully find some volunteers to write regression tests), then new APIs to existing classes will need to be considered carefully and implemented in extensions. So there will be some extension of IUIBase that has some new API instead of adding new APIs to IUIBase. I have a personal preference to use long names instead of numbers, so the extension will hopefully be called IUIBaseWithWhatever instead of IUIBase2.
>
> If you are asking about build-time versioning, we haven't done anything there either. As long as there is no impact on production apps I think it is fine for folks to contribute something if there is a need.
>
> My 2 cents,
> -Alex
>
>
> -Mark K
>
> -----Original Message-----
> From: Alex Harui [mailto:aharui@adobe.com.INVALID <ma...@adobe.com.INVALID>]
> Sent: Friday, April 26, 2019 2:44 AM
> To: dev@royale.apache.org
> Subject: [Non-DoD Source] Re: Let's bump Royale version to 1.0
>
> I do not have an opinion on what technical/marketing criteria we use to decide which release to call 1.0. I'm not working directly with users/customers.
>
> I do not currently have time/energy/budget to work on any of the things folks think need to be done to get to 1.0 and barely have enough time to work on getting the next release out. So someone else will have to supply the time/energy/budget to get these tasks done.
>
> I do have an opinion based on a practical aspect. So far, we have not had the release scripts properly generate the right version number for the NPM artifacts. That's why we've jumped from 0.9.4 to 0.9.6 and skipped 0.9.5. So I would say we should not call this next release 1.0 and wait until the release automation can correctly version all artifacts with the right version number before we pick one to call 1.0. With any luck I'll get the automation running next week and will ask for someone to volunteer to test drive it.
>
> -Alex
>
>
>
> ----- Message from Apache Royale CI Server <ap...@gmail.com> on Fri, 26 Apr 2019 21:49:11 +0000 (UTC) -----
> To:
> dev@royale.apache.org
> Subject:
> Release Step 001 Succeeded
> Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001 and run the following commands:
> git push
> git checkout release/0.9.6
> git push -u origin release/0.9.6
>
> You will need your Apache/Github username and 2FA token.
> ----- Message from Apache Royale CI Server <ap...@gmail.com> on Fri, 26 Apr 2019 22:05:55 +0000 (UTC) -----
> To:
> dev@royale.apache.org
> Subject:
> Release Step 001a Succeeded
> Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_001a_If_Utils and run the following commands:
> git push
>
> You will need your Apache/Github username and 2FA token.
> ----- Message from Apache Royale CI Server <ap...@gmail.com> on Fri, 26 Apr 2019 22:29:43 +0000 (UTC) -----
> To:
> dev@royale.apache.org
> Subject:
> Release Step 002 Succeeded
> Log in to the server, open a command prompt, change directory to C:\jenkins\workspace\Royale_Release_Step_002 and run the following commands:
> git push
> git push origin org.apache.royale.compiler-0.9.6-rc1
>
> You will need your Apache/Github username and 2FA token.
> ----- Message from Apache Royale CI Server <ap...@gmail.com> on Fri, 26 Apr 2019 22:36:43 +0000 (UTC) -----
> To:
> dev@royale.apache.org
> Subject:
> Release Step 002a Succeeded
> Continue on to Release Step 003
> ----- Message from Apache Royale CI Server <ap...@gmail.com> on Fri, 26 Apr 2019 22:46:49 +0000 (UTC) -----
> To:
> dev@royale.apache.org
> Subject:
> Release Step 003 Succeeded
> 1. If you are releasing the utils jars (compiler-jburg-types and compiler-build-tools), Run:
> ant -f releasesteps.xml Release_Step_003 -Dutils=true -Drelease.version=0.9.6
> Otherwise, Run:
> ant -f releasesteps.xml Release_Step_003 -Drelease.version=0.9.6
> This will download the artifacts then unzip and compile the source artifact.
> 2. Validate that the compiled artifacts match the downloaded artifacts.
> 3. If they do, then run ant -f releasesteps.xml Release_Step_003_Sign -Drelease.version=0.9.6
> This will PGP sign the source ZIP and compiled JARs
> 4. Then run ant -f releasesteps.xml Release_Step_003_Upload -Drelease.version=0.9.6
> This will upload the signed artifacts to Maven Release Staging. Do not "Close" the staging repository until the other repos have been added.
> ----- Message from Apache Royale CI Server <ap...@gmail.com> on Sat, 27 Apr 2019 03:57:52 +0000 (UTC) -----
> To:
> dev@royale.apache.org
> Subject:
> Build failed in Jenkins: royale-asjs_MXTests #722
> See <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/722/display/redirect <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/722/display/redirect>>
>
> ------------------------------------------
> [...truncated 2.03 MB...]
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataGridModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataGridModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/DataGridModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/DataGridModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IState.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IState.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataDefinition.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataDefinition.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ISpinnerView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/SpinnerView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IViewportModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IViewportModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/WrappedHTMLElement.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/WrappedHTMLElement.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/DropLocation.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/DropLocation.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/layout/LayoutData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/errors/CursorError.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/errors/CursorError.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/TextLineMetrics.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/TextLineMetrics.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/CSSStyleDeclaration.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/CSSStyleDeclaration.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/FocusEventConverter.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/FocusEventConverter.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MethodDefinition.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MethodDefinition.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/display/Graphics.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/display/Graphics.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollControlBase.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollControlBase.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/ListBase.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/ListBase.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataProviderVirtualItemRendererMapper.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataProviderVirtualItemRendererMapper.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/WatcherBase.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/WatcherBase.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImage.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IImage.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/BrowserEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/BrowserEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/PanelModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/PanelModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/models/PanelModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/models/PanelModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IPopUp.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IPopUp.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ButtonTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ButtonTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/scripts/ButtonTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/scripts/ButtonTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBase.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBase.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateField.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateField.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/RoyaleContext.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/RoyaleContext.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ContainerBaseStrandChildren.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ContainerBaseStrandChildren.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/BinaryData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/UIUtils.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/UIUtils.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ListSingleSelectionMouseController.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ListSingleSelectionMouseController.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuBarMouseController.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuBarMouseController.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/controllers/MenuBarMouseController.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/controllers/MenuBarMouseController.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/CollectionEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/CollectionEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/menuClasses/MenuBarItemRenderer.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/menuClasses/MenuBarItemRenderer.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/accessories/PasswordInputBead.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/accessories/PasswordInputBead.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/managers/ICursorManager.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/managers/ICursorManager.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/MenuBarTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/MenuBarTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/BaseListData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/BaseListData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/HorizontalFlexLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/HorizontalFlexLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/ButtonBarLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/ButtonBarLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/SendFormattedResultsToLog.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/SendFormattedResultsToLog.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/utils/EventUtils.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/utils/EventUtils.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/ToolTip.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/ToolTip.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuSelectionMouseController.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/MenuSelectionMouseController.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataGrid.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IDataGrid.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IMenuBarModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IMenuBarModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/MenuBarModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/MenuBarModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/NumericStepperView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/NumericStepperView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/LayoutElementHelper.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/LayoutElementHelper.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/TestResult.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/TestResult.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IFactory.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IFactory.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/BasicLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/BasicLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/getDefinitionByName.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/getDefinitionByName.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/List.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/List.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/Strand.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/Strand.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ValueEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ValueEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/IXMLNotifiable.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/IXMLNotifiable.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/XMLListAdapter.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/XMLListAdapter.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/utils/KeyboardEventConverter.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/utils/KeyboardEventConverter.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ItemClickedEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ItemClickedEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/EffectTimer.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/EffectTimer.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/DayNameItemRenderer.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/DayNameItemRenderer.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/styles/BorderStyles.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/styles/BorderStyles.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/states/State.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/states/State.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/states/State.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/states/State.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ContainerLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ContainerLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/MenuModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/MenuModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/CallLaterBead.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/CallLaterBead.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/ToolTipBead.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/ToolTipBead.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/utilityClasses/FlexChildInfo.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/utilityClasses/FlexChildInfo.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/OSUtils.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/OSUtils.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/KeyboardEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/KeyboardEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/KeyboardEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/KeyboardEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateChooser.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DateChooser.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/resources/LocaleSorter.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/resources/LocaleSorter.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/describeType.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/describeType.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/DisableBead.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/DisableBead.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IToggleButtonModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IToggleButtonModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/DataBindingBase.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/DataBindingBase.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ContainerDataBinding.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ContainerDataBinding.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/TestCase.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/TestCase.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/StyleManager.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/StyleManager.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/BoxLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/BoxLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/geom/Point.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/geom/Point.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/DateHeaderButton.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/DateHeaderButton.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/HBox.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/HBox.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/LayoutElementUIComponentUtils.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/LayoutElementUIComponentUtils.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/CheckBoxTests.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/CheckBoxTests.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/ListEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/ListEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/KeyboardEventConverter.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/utils/KeyboardEventConverter.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/BasicLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/BasicLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/DataGridColumnList.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/DataGridColumnList.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/VerticalFlexLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/VerticalFlexLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/debugging/assert.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/debugging/assert.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/StringUtil.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/StringUtil.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/Label.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/Label.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/VerticalLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/VerticalLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ListView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ListView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/MenuView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/MenuView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/GenericBinding.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/GenericBinding.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ValueChangeEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/ValueChangeEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ITextFieldFactory.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ITextFieldFactory.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/TextArea.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/TextArea.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/DateFieldTests.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/DateFieldTests.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ImageView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ImageView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/MXMLBeadViewDataBinding.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/MXMLBeadViewDataBinding.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/conversions/createEventInit.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/conversions/createEventInit.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/StringUtil.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/StringUtil.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/ViewportModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/ViewportModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/ArrayList.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/ArrayList.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/SingleSelectionIListModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/SingleSelectionIListModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/DataGridButtonBar.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/DataGridButtonBar.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/net/IDataOutput.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/net/IDataOutput.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/ApplicationLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/ApplicationLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ComboBoxView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ComboBoxView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/PanelView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/PanelView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/states/AddItems.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/states/AddItems.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/TextAreaTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/TextAreaTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/components/beads/GroupView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/components/beads/GroupView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/PointUtils.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/PointUtils.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/PanelView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/beads/PanelView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/TextItemRendererFactoryForArrayData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/TextItemRendererFactoryForArrayData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/DisabledAlphaBead.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/DisabledAlphaBead.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/PanelLayoutProxy.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/PanelLayoutProxy.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/buttonBarClasses/TextButtonDataGridColumnItemRenderer.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/buttonBarClasses/TextButtonDataGridColumnItemRenderer.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/ButtonTests.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/ButtonTests.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/geom/Rectangle.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/geom/Rectangle.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ItemRendererClassFactory.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ItemRendererClassFactory.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DataGrid.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/DataGrid.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/NumericStepper.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/NumericStepper.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/ISortField.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/ISortField.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/SortField.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/SortField.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollPolicy.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/ScrollPolicy.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/Namespace.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/Namespace.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/FlexCSSStyles.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/FlexCSSStyles.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/LayoutChangeNotifier.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/LayoutChangeNotifier.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/SortFieldCompareTypes.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/collections/SortFieldCompareTypes.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/debugging/assertType.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/debugging/assertType.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/IPropertyChangeNotifier.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/IPropertyChangeNotifier.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ButtonBarView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/ButtonBarView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/RadioButtonGroup.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/RadioButtonGroup.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/IFactory.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/IFactory.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/MenuFactory.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/MenuFactory.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/SimpleCSSStylesWithFlex.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/SimpleCSSStylesWithFlex.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/PanelTitleBar.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/containers/PanelTitleBar.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/states/SetEventHandler.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/states/SetEventHandler.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/DateFieldTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/DateFieldTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/AllCSSValuesImpl.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/AllCSSValuesImpl.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ListAndDataGridTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/ListAndDataGridTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/DateFieldMouseController.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/DateFieldMouseController.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/CloseButton.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/CloseButton.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/getQualifiedClassName.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/getQualifiedClassName.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/PropertyChangeEventKind.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/PropertyChangeEventKind.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/utils/MouseEventConverter.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/utils/MouseEventConverter.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ConstantBinding.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ConstantBinding.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBox.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/ComboBox.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/EdgeMetrics.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/EdgeMetrics.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IScrollingViewport.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IScrollingViewport.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/TitleBarView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/TitleBarView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/SingleSelectionICollectionViewModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/SingleSelectionICollectionViewModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/ComboBoxModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/beads/models/ComboBoxModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/TypeDefinition.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/TypeDefinition.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/ObjectUtil.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/utils/ObjectUtil.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/validators/ValidationResult.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/validators/ValidationResult.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/MouseEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/events/MouseEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/MouseEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/MouseEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/XML.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/XML.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/Image.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/Image.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/SparkLayoutBead.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/layouts/supportClasses/SparkLayoutBead.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/DataItemRendererFactoryForArrayData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/DataItemRendererFactoryForArrayData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/FocusEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/FocusEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/ToggleButtonModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/ToggleButtonModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/VirtualDataItemRendererFactoryForIListData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/VirtualDataItemRendererFactoryForIListData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ClassFactory.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/ClassFactory.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ChainBinding.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/ChainBinding.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/Keyboard.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/Keyboard.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/ExitWhenDone.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/ExitWhenDone.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/dataGridClasses/DataGridColumn.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/dataGridClasses/DataGridColumn.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/QName.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/QName.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/SpinnerButton.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/SpinnerButton.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/dateFieldClasses/DateFieldDateChooser.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/dateFieldClasses/DateFieldDateChooser.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/PropertyWatcher.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/binding/PropertyWatcher.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/ScrollingViewport.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/ScrollingViewport.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/AssertPropertyValue.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/AssertPropertyValue.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/ListAndDataGridTests.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/ListAndDataGridTests.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/MenuEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/MenuEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/DataProviderModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/DataProviderModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/TextInputTestScript.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/scripts/TextInputTestScript.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/PropertyChangeEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/PropertyChangeEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IRangeModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/core/IRangeModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/effects/Effect.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/effects/Effect.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/TextAreaTests.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/halo/views/TextAreaTests.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/Timer.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/utils/Timer.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/FlexEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/FlexEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/managers/FocusManager.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/managers/FocusManager.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/RangeModel.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/models/RangeModel.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataArgDefinition.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/reflection/MetaDataArgDefinition.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/ComboBoxList.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/supportClasses/ComboBoxList.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ItemRendererMouseController.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/controllers/ItemRendererMouseController.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/ValidationResultEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/events/ValidationResultEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/StyleManagerImpl.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/styles/StyleManagerImpl.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/collections/ICollection.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/collections/ICollection.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/mx_internal.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/core/mx_internal.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/core/NavigationUnit.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/spark/core/NavigationUnit.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/DispatchMouseClickEvent.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/DispatchMouseClickEvent.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/TileLayout.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/html/beads/layouts/TileLayout.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/DataItemRendererFactoryForICollectionViewData.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/mx/controls/listClasses/DataItemRendererFactoryForICollectionViewData.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/collections/ICollectionView.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/org/apache/royale/collections/ICollectionView.js>>
> [mxmlc] using source file: <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/BasicTests_mx_managers_SystemManager.js <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/bin/js-debug/BasicTests_mx_managers_SystemManager.js>>
> [mxmlc] The project 'BasicTests' has been successfully compiled.
> [mxmlc] 22.9818728 seconds
> [mxmlc] <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/MenuBarTests.mxml(33) <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/MenuBarTests.mxml(33)>>: col: 5 Warning: public var may not work in minified JS output. Use getter/setter instead.
> [mxmlc]
> [mxmlc] public var menuBarDP:Object = {label: "top", children: [
> [mxmlc] ^
> [mxmlc]
> [mxmlc] <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/ListAndDataGridTests.mxml(35) <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/ListAndDataGridTests.mxml(35)>>: col: 5 Warning: public var may not work in minified JS output. Use getter/setter instead.
> [mxmlc]
> [mxmlc] public var listDP:Array = [
> [mxmlc] ^
> [mxmlc]
> [mxmlc] <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/ListAndDataGridTests.mxml(44) <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/ListAndDataGridTests.mxml(44)>>: col: 5 Warning: public var may not work in minified JS output. Use getter/setter instead.
> [mxmlc]
> [mxmlc] public var dataGridDP:Array =
> [mxmlc] ^
> [mxmlc]
> [mxmlc] <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/ComboBoxTests.mxml(33) <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/halo/views/ComboBoxTests.mxml(33)>>: col: 2 Warning: public var may not work in minified JS output. Use getter/setter instead.
> [mxmlc]
> [mxmlc] public var comboDP:Array = ["Apples", "Beer", "Soda", "Pears", "Peaches", "Bagels"];
> [mxmlc] ^
> [mxmlc]
> [mxmlc] Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g
> [echo] launching player and swf C:\adobe\flash\11.7\flashplayerdebugger.exe <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/BasicTests.swf <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/mustella/tests/mxtests/basicTests/BasicTests.swf>>
>
> mustellaresultsparser:
> [java] test case ListTest1&result=fail&elapsed=3&phase=body&started=1556337469490&extraInfo=&msg=TypeError: failed
> [java] results: FAILED
>
> BUILD FAILED
> <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/build.xml <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/build.xml>>:1589: The following error occurred while executing this line:
> <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/build.xml <http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_MXTests/ws/build.xml>>:1516: Java returned: 1
>
> Total time: 9 minutes 44 seconds
> Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF-8 -Xms384m -Xmx1g
> Build step 'Invoke Ant' marked build as failure
>
>
>
>