Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

2018-02-09 Thread Erik de Bruin
>
> I also notice that google search has picked up content on
> http://royale.codeoscopic.com and http://www.royalesdk.org domains. This
> may be a little confusing brand wise for users searching for the project.
> It's also picking test pages and the like from
> http://royale.codeoscopic.com and pages with text like "Dicat scripta
> percipit vim in, vidit atomorum cum cu.” I thought trademarks asked to have
> http://www.royalesdk.org redirect to http://royale.apache.org? Currently
> it’s still redirecting to http://royale.codeoscopic.com.
>

This is not related to the release. I'm starting another thread.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295 <06%2051952295>
I. www.ixsoftware.nl


Development website indexing issues (was Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1)

2018-02-09 Thread Erik de Bruin
In the release thread Justin wrote:


> [...] trademarks asked to have http://www.royalesdk.org redirect to
> http://royale.apache.org? Currently it’s still redirecting to
> http://royale.codeoscopic.com.
>

I am the current owner of that domain. I wasn't aware of a request by
trademarks. The 'www' domain already had the proper redirection, but the
'bare' domain ("http://royalesdk.org;) did not. I have changed the DNS
record to fix the issue. It'll take some time to propagate to all corners
of the interwebs.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Ant Build Problem

2017-12-19 Thread Erik de Bruin
"apache-flex-flexunit-4.2.0-4.12.0-bin.zip" is downloaded and unzipped to
the 'royale-asjs/in' directory. I have no other FlexUnit on my system.

EdB



On Tue, Dec 19, 2017 at 7:47 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> Erik,
>
> What FlexUnit are you running?  My guess is it is different than the one
> the rest of are running.
>
> -Alex
>
> On 12/19/17, 3:15 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
> >Some more trace:
> >
> >Created dir:
> >/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/r
> >oyale/out
> > [flexunit] Validating task attributes ...
> > [flexunit] Generating default values ...
> > [flexunit] Using the following settings for the test run:
> > [flexunit] haltonfailure: [false]
> > [flexunit] headless: [false]
> > [flexunit] display: [99]
> > [flexunit] localTrusted: [true]
> > [flexunit] player: [flash]
> > [flexunit] port: [1024]
> > [flexunit] swf:
> >[/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/
> >royale/FlexUnitRoyaleApplication.swf]
> > [flexunit] timeout: [9ms]
> > [flexunit] toDir:
> >[/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/
> >royale/out]
> > [flexunit] Setting up server process ...
> > [flexunit] Starting server ...
> > [flexunit] Entry
> >[/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/
> >royale]
> >already available in local trust file at
> >[/Users/erik/Library/Preferences/Macromedia/Flash
> >Player/#Security/FlashPlayerTrust/flexUnit.cfg].
> > [flexunit] Executing 'open' with arguments:
> > [flexunit]
> >'/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/
> >royale/FlexUnitRoyaleApplication.swf'
> > [flexunit]
> > [flexunit] The ' characters around the executable and arguments are
> > [flexunit] not part of the command.
> > [flexunit]
> > [flexunit] Opening server socket on port [1024].
> > [flexunit] Waiting for client connection ...
> >
> >HTH,
> >
> >EdB
> >
> >
> >
> >On Tue, Dec 19, 2017 at 12:14 PM, Erik de Bruin <e...@ixsoftware.nl>
> >wrote:
> >
> >> I get an error dialog from the swf being tested, "VerifyError: Error
> >> #1014: Class IResponder could not be found.". When I dismiss the dialog,
> >> test test times out and the ant build fails.
> >>
> >> EdB
> >>
> >>
> >>
> >> On Tue, Dec 19, 2017 at 11:25 AM, Alex Harui <aha...@adobe.com.invalid>
> >> wrote:
> >>
> >>> What error do you get if you don't apply the workaround?
> >>>
> >>> -Alex
> >>>
> >>> On 12/19/17, 2:02 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> >>>
> >>> >Just to keep this fresh:
> >>> >
> >>> >This is still an issue, and the workaround below is required for me
> >>>to be
> >>> >able to run 'ant' on the royale-asjs project...
> >>> >
> >>> >EdB
> >>> >
> >>> >
> >>> >
> >>> >On Thu, Nov 16, 2017 at 8:01 AM, Erik de Bruin <e...@ixsoftware.nl>
> >>> wrote:
> >>> >
> >>> >> I did several fresh pulls of the repos yesterday while testing
> >>>as2wasm
> >>> >>and
> >>> >> I can faithfully reproduce the issue(s). I can also reliably make
> >>>it go
> >>> >> away if I do these things:
> >>> >>
> >>> >> - comment out the ant task in the 'CoreTest' target in
> >>> >>frameworks/build.xml
> >>> >> - remove the 'test' dependency from the 'main' target in
> >>> >> frameworks/projects/Basic/build.xml
> >>> >>
> >>> >> HTH,
> >>> >>
> >>> >> EdB
> >>> >>
> >>> >>
> >>> >>
> >>> >> On Thu, Nov 16, 2017 at 7:43 AM, Yishay Weiss
> >>><yishayj...@hotmail.com>
> >>> >> wrote:
> >>> >>
> >>> >>> Thanks for the pointers Alex. Funnily I stopped getting it after
> >>> >>>playing
> >>> >>> around with some scripts, cleaning my changes and checking out from
> >>> >>>git the
> >>> >>> unit t

Re: Ant Build Problem

2017-12-19 Thread Erik de Bruin
Some more trace:

Created dir:
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/out
 [flexunit] Validating task attributes ...
 [flexunit] Generating default values ...
 [flexunit] Using the following settings for the test run:
 [flexunit] haltonfailure: [false]
 [flexunit] headless: [false]
 [flexunit] display: [99]
 [flexunit] localTrusted: [true]
 [flexunit] player: [flash]
 [flexunit] port: [1024]
 [flexunit] swf:
[/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/FlexUnitRoyaleApplication.swf]
 [flexunit] timeout: [9ms]
 [flexunit] toDir:
[/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/out]
 [flexunit] Setting up server process ...
 [flexunit] Starting server ...
 [flexunit] Entry
[/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale]
already available in local trust file at
[/Users/erik/Library/Preferences/Macromedia/Flash
Player/#Security/FlashPlayerTrust/flexUnit.cfg].
 [flexunit] Executing 'open' with arguments:
 [flexunit]
'/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/FlexUnitRoyaleApplication.swf'
 [flexunit]
 [flexunit] The ' characters around the executable and arguments are
 [flexunit] not part of the command.
 [flexunit]
 [flexunit] Opening server socket on port [1024].
 [flexunit] Waiting for client connection ...

HTH,

EdB



On Tue, Dec 19, 2017 at 12:14 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> I get an error dialog from the swf being tested, "VerifyError: Error
> #1014: Class IResponder could not be found.". When I dismiss the dialog,
> test test times out and the ant build fails.
>
> EdB
>
>
>
> On Tue, Dec 19, 2017 at 11:25 AM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
>> What error do you get if you don't apply the workaround?
>>
>> -Alex
>>
>> On 12/19/17, 2:02 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>
>> >Just to keep this fresh:
>> >
>> >This is still an issue, and the workaround below is required for me to be
>> >able to run 'ant' on the royale-asjs project...
>> >
>> >EdB
>> >
>> >
>> >
>> >On Thu, Nov 16, 2017 at 8:01 AM, Erik de Bruin <e...@ixsoftware.nl>
>> wrote:
>> >
>> >> I did several fresh pulls of the repos yesterday while testing as2wasm
>> >>and
>> >> I can faithfully reproduce the issue(s). I can also reliably make it go
>> >> away if I do these things:
>> >>
>> >> - comment out the ant task in the 'CoreTest' target in
>> >>frameworks/build.xml
>> >> - remove the 'test' dependency from the 'main' target in
>> >> frameworks/projects/Basic/build.xml
>> >>
>> >> HTH,
>> >>
>> >> EdB
>> >>
>> >>
>> >>
>> >> On Thu, Nov 16, 2017 at 7:43 AM, Yishay Weiss <yishayj...@hotmail.com>
>> >> wrote:
>> >>
>> >>> Thanks for the pointers Alex. Funnily I stopped getting it after
>> >>>playing
>> >>> around with some scripts, cleaning my changes and checking out from
>> >>>git the
>> >>> unit tests aren’t being run anymore and so I’m not getting it. I’ll
>> >>>come
>> >>> back to it when it starts itching again, but for now I can work.
>> >>>
>> >>>
>> >>>
>> >>> 
>> >>> From: Alex Harui <aha...@adobe.com.INVALID>
>> >>> Sent: Wednesday, November 15, 2017 6:41:20 PM
>> >>> To: dev@royale.apache.org
>> >>> Subject: Re: Ant Build Problem
>> >>>
>> >>> My working copies are all torn up with the refactoring and I'd prefer
>> >>>not
>> >>> to have to stop and build up another working copy to debug this,
>> >>>assuming
>> >>> I can even reproduce it.
>> >>>
>> >>> The factors are:
>> >>> -The compiler Ant tasks use ROYALE_COMPILER_HOME to find the jsc.jar
>> to
>> >>> run
>> >>> -Looks like there are bugs in the scripts where ROYALE_COMPILER_HOME
>> is
>> >>> not set by each script but maybe only the main script
>> >>> -The FlexUnit compile should be using frameworks/royale-config.xml
>> >>> -The royale-config.xml should have:
>> >>>   COMPILE::SWFAUTO
>> >>>   COMPILE::JSAUTO
>> >>> -Recent (0.8.0 and later) co

Re: Ant Build Problem

2017-12-19 Thread Erik de Bruin
I get an error dialog from the swf being tested, "VerifyError: Error #1014:
Class IResponder could not be found.". When I dismiss the dialog, test test
times out and the ant build fails.

EdB



On Tue, Dec 19, 2017 at 11:25 AM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> What error do you get if you don't apply the workaround?
>
> -Alex
>
> On 12/19/17, 2:02 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
> >Just to keep this fresh:
> >
> >This is still an issue, and the workaround below is required for me to be
> >able to run 'ant' on the royale-asjs project...
> >
> >EdB
> >
> >
> >
> >On Thu, Nov 16, 2017 at 8:01 AM, Erik de Bruin <e...@ixsoftware.nl>
> wrote:
> >
> >> I did several fresh pulls of the repos yesterday while testing as2wasm
> >>and
> >> I can faithfully reproduce the issue(s). I can also reliably make it go
> >> away if I do these things:
> >>
> >> - comment out the ant task in the 'CoreTest' target in
> >>frameworks/build.xml
> >> - remove the 'test' dependency from the 'main' target in
> >> frameworks/projects/Basic/build.xml
> >>
> >> HTH,
> >>
> >> EdB
> >>
> >>
> >>
> >> On Thu, Nov 16, 2017 at 7:43 AM, Yishay Weiss <yishayj...@hotmail.com>
> >> wrote:
> >>
> >>> Thanks for the pointers Alex. Funnily I stopped getting it after
> >>>playing
> >>> around with some scripts, cleaning my changes and checking out from
> >>>git the
> >>> unit tests aren’t being run anymore and so I’m not getting it. I’ll
> >>>come
> >>> back to it when it starts itching again, but for now I can work.
> >>>
> >>>
> >>>
> >>> 
> >>> From: Alex Harui <aha...@adobe.com.INVALID>
> >>> Sent: Wednesday, November 15, 2017 6:41:20 PM
> >>> To: dev@royale.apache.org
> >>> Subject: Re: Ant Build Problem
> >>>
> >>> My working copies are all torn up with the refactoring and I'd prefer
> >>>not
> >>> to have to stop and build up another working copy to debug this,
> >>>assuming
> >>> I can even reproduce it.
> >>>
> >>> The factors are:
> >>> -The compiler Ant tasks use ROYALE_COMPILER_HOME to find the jsc.jar to
> >>> run
> >>> -Looks like there are bugs in the scripts where ROYALE_COMPILER_HOME is
> >>> not set by each script but maybe only the main script
> >>> -The FlexUnit compile should be using frameworks/royale-config.xml
> >>> -The royale-config.xml should have:
> >>>   COMPILE::SWFAUTO
> >>>   COMPILE::JSAUTO
> >>> -Recent (0.8.0 and later) compilers should convert AUTO to a valid
> >>>value
> >>> for the compile.
> >>>
> >>>
> >>> HTH,
> >>> -Alex
> >>>
> >>> On 11/15/17, 7:48 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> >>>
> >>> >I see the same issue! I am trying to write a quick tutorial for the
> >>>new
> >>> >wasm code, but I still can't successfully run "ant super-clean all" on
> >>> >royale-asjs... Please help?
> >>> >
> >>> >compile:
> >>> > [echo] Compiling FlexUnitRoyaleApplication.swf
> >>> > [echo] ROYALE_HOME: /Users/erik/Desktop/tmp/royale-asjs
> >>> > [echo] ROYALE_SWF_COMPILER_HOME: /Users/erik/Desktop/tmp/royale
> >>> -asjs
> >>> > [echo] FLEXUNIT_HOME: /Users/erik/Desktop/tmp/royale
> >>> -asjs/in/flexunit
> >>> > [echo] playerglobal.version: 11.1
> >>> >[mxmlc] MXMLJSC
> >>> >[mxmlc] -debug
> >>> >[mxmlc] -compiler.targets=SWF
> >>> >[mxmlc] +playerglobal.version=11.1
> >>> >[mxmlc]
> >>>
> >>>>+env.PLAYERGLOBAL_HOME=/Users/erik/Documents/Royale/
> PlayerGlobal/player
> >>> >[mxmlc]
> >>> >-swf-library-path+=/Users/erik/Desktop/tmp/royale-asjs/
> frameworks/libs
> >>> >[mxmlc]
> >>> >-swf-library-path+=/Users/erik/Desktop/tmp/royale-asjs/in/
> >>> flexunit/flexuni
> >>> >t
> >>> >[mxmlc] -define=CONFIG::dummy,false
> >>> >[mxmlc] +royalelib=/Users/erik/Desktop/tmp/ro

Re: Ant Build Problem

2017-12-19 Thread Erik de Bruin
Just to keep this fresh:

This is still an issue, and the workaround below is required for me to be
able to run 'ant' on the royale-asjs project...

EdB



On Thu, Nov 16, 2017 at 8:01 AM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> I did several fresh pulls of the repos yesterday while testing as2wasm and
> I can faithfully reproduce the issue(s). I can also reliably make it go
> away if I do these things:
>
> - comment out the ant task in the 'CoreTest' target in frameworks/build.xml
> - remove the 'test' dependency from the 'main' target in
> frameworks/projects/Basic/build.xml
>
> HTH,
>
> EdB
>
>
>
> On Thu, Nov 16, 2017 at 7:43 AM, Yishay Weiss <yishayj...@hotmail.com>
> wrote:
>
>> Thanks for the pointers Alex. Funnily I stopped getting it after playing
>> around with some scripts, cleaning my changes and checking out from git the
>> unit tests aren’t being run anymore and so I’m not getting it. I’ll come
>> back to it when it starts itching again, but for now I can work.
>>
>>
>>
>> 
>> From: Alex Harui <aha...@adobe.com.INVALID>
>> Sent: Wednesday, November 15, 2017 6:41:20 PM
>> To: dev@royale.apache.org
>> Subject: Re: Ant Build Problem
>>
>> My working copies are all torn up with the refactoring and I'd prefer not
>> to have to stop and build up another working copy to debug this, assuming
>> I can even reproduce it.
>>
>> The factors are:
>> -The compiler Ant tasks use ROYALE_COMPILER_HOME to find the jsc.jar to
>> run
>> -Looks like there are bugs in the scripts where ROYALE_COMPILER_HOME is
>> not set by each script but maybe only the main script
>> -The FlexUnit compile should be using frameworks/royale-config.xml
>> -The royale-config.xml should have:
>>   COMPILE::SWFAUTO
>>   COMPILE::JSAUTO
>> -Recent (0.8.0 and later) compilers should convert AUTO to a valid value
>> for the compile.
>>
>>
>> HTH,
>> -Alex
>>
>> On 11/15/17, 7:48 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>>
>> >I see the same issue! I am trying to write a quick tutorial for the new
>> >wasm code, but I still can't successfully run "ant super-clean all" on
>> >royale-asjs... Please help?
>> >
>> >compile:
>> > [echo] Compiling FlexUnitRoyaleApplication.swf
>> > [echo] ROYALE_HOME: /Users/erik/Desktop/tmp/royale-asjs
>> > [echo] ROYALE_SWF_COMPILER_HOME: /Users/erik/Desktop/tmp/royale
>> -asjs
>> > [echo] FLEXUNIT_HOME: /Users/erik/Desktop/tmp/royale
>> -asjs/in/flexunit
>> > [echo] playerglobal.version: 11.1
>> >[mxmlc] MXMLJSC
>> >[mxmlc] -debug
>> >[mxmlc] -compiler.targets=SWF
>> >[mxmlc] +playerglobal.version=11.1
>> >[mxmlc]
>> >+env.PLAYERGLOBAL_HOME=/Users/erik/Documents/Royale/PlayerGlobal/player
>> >[mxmlc]
>> >-swf-library-path+=/Users/erik/Desktop/tmp/royale-asjs/frameworks/libs
>> >[mxmlc]
>> >-swf-library-path+=/Users/erik/Desktop/tmp/royale-asjs/in/
>> flexunit/flexuni
>> >t
>> >[mxmlc] -define=CONFIG::dummy,false
>> >[mxmlc] +royalelib=/Users/erik/Desktop/tmp/royale-asjs/frameworks/
>> >[mxmlc]
>> >-output=/Users/erik/Desktop/tmp/royale-asjs/frameworks/proj
>> ects/Core/src/t
>> >est/royale/FlexUnitRoyaleApplication.swf
>> >[mxmlc] --
>> >[mxmlc]
>> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/projects/
>> Core/src/test/roya
>> >le/FlexUnitRoyaleApplication.mxml
>> >[mxmlc] Loading configuration:
>> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/royale-config.xml
>> >[mxmlc]
>> >[mxmlc] scanning for overrides: IFlexInfo
>> >
>> >
>> >
>> >[mxmlc] scanning for overrides: StringTrimmer
>> >[mxmlc] 2.498695566 seconds
>> >[mxmlc]
>> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/projects/
>> Core/src/test/roya
>> >le/flexUnitTests/KeyboardEventConverterTest.as(23):
>> >col: 5 Error: Can not resolve config constant: 'SWF'
>> >[mxmlc]
>> >[mxmlc] COMPILE::SWF
>> >[mxmlc] ^
>> >[mxmlc]
>> >[mxmlc]
>> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/projects/
>> Core/src/test/roya
>> >le/flexUnitTests/KeyboardEventConverterTest.as(56):
>> >col: 13 Error: Can not resolve config constant: 'SWF'
>> >[mxmlc]
>> >[mxml

Re: Access to build servers

2017-12-19 Thread Erik de Bruin
I guess I am... I want to look at the settings for some of the builds, and
I think I need to be logged in to do that, right?

EdB



On Tue, Dec 19, 2017 at 10:44 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
wrote:

> Erik,
>
> You basically wanted to access to the remote machine yes ? That's what you
> are asking ?
>
> Thanks, Piotr
>
>
> 2017-12-19 10:42 GMT+01:00 Erik de Bruin <e...@ixsoftware.nl>:
>
> > I do, but I didn't know where they lived :-)
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> > On Tue, Dec 19, 2017 at 10:04 AM, Piotr Zarzycki <
> > piotrzarzyck...@gmail.com>
> > wrote:
> >
> > > Hi Erik,
> > >
> > > Are you asking about that [1] ? You don't have access to that severs ?
> > >
> > > [1] http://apacheflexbuild.cloudapp.net:8080/
> > > [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/
> > > [3] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
> > >
> > > Thanks, Piotr
> > >
> > >
> > > 2017-12-19 9:23 GMT+01:00 Erik de Bruin <e...@ixsoftware.nl>:
> > >
> > > > Hi,
> > > >
> > > > Where can I find the build servers (URLs) and how can I access the
> > > > settings?
> > > >
> > > > I'm having great difficulty getting the compiler projects to work in
> > > > Eclipse, mainly due to a lot of tests (~30%) failing. Alex informed
> me
> > > that
> > > > all tests are passing on the build servers, so I would like to take a
> > > peek
> > > > at the settings.
> > > >
> > > > Thanks,
> > > >
> > > > EdB
> > > >
> > > >
> > > >
> > > > --
> > > > Ix Multimedia Software
> > > >
> > > > Jan Luykenstraat 27
> > > > 3521 VB Utrecht
> > > >
> > > > T. 06-51952295
> > > > I. www.ixsoftware.nl
> > > >
> > >
> > >
> > >
> > > --
> > >
> > > Piotr Zarzycki
> > >
> > > Patreon: *https://www.patreon.com/piotrzarzycki
> > > <https://www.patreon.com/piotrzarzycki>*
> > >
> >
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Access to build servers

2017-12-19 Thread Erik de Bruin
I do, but I didn't know where they lived :-)

Thanks,

EdB



On Tue, Dec 19, 2017 at 10:04 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
wrote:

> Hi Erik,
>
> Are you asking about that [1] ? You don't have access to that severs ?
>
> [1] http://apacheflexbuild.cloudapp.net:8080/
> [2] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/
> [3] http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs-jsonly/
>
> Thanks, Piotr
>
>
> 2017-12-19 9:23 GMT+01:00 Erik de Bruin <e...@ixsoftware.nl>:
>
> > Hi,
> >
> > Where can I find the build servers (URLs) and how can I access the
> > settings?
> >
> > I'm having great difficulty getting the compiler projects to work in
> > Eclipse, mainly due to a lot of tests (~30%) failing. Alex informed me
> that
> > all tests are passing on the build servers, so I would like to take a
> peek
> > at the settings.
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Try-it-now app] Progress thread

2017-11-28 Thread Erik de Bruin
Olaf,

>The instance has a basic PHP stack on it
> Although I'm doing PHP since PHP3 I would prefer to go with NodeJS and a
> NoSQL DB here.
> I am still learning NodeJS but it seems to me it is straightforward and we
> also could implement some real time stuff maybe a bit easier. (I think in a
> more matured try-it-now version some day it would be cool to return the
> compiler log in real time to the app instead of just showing a spinner)
>
> Is it a big task with AWS to create a NodeJS instance and to install
> additional npm's?
>

I put that PHP stack on there, I can take it off easily enough. Anyone I
give SSH access to can do it.

I do not know enough to create a NodeJS stack, nor am I familiar with NoSQL
databases. But I'm sure someone else is, and I can provide them access to
set it up.

If we're not going to use the MySQL database, please let me know a.s.a.p.,
as that is incurring additional costs on my AWS account.

Om, how much of Olaf's requests can you deliver, if I give you the access
needed?

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Try-it-now app] Progress thread

2017-11-27 Thread Erik de Bruin
> > I'll point a subdomain of the royalesdk.org domain to it, just because I
> > can ;-)
> >
>
> Please don't.  We don't want a trademarks discussion at this point :-)
>


No fun! No fair!

:-)

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295 <06%2051952295>
I. www.ixsoftware.nl


Re: [Try-it-now app] Progress thread

2017-11-27 Thread Erik de Bruin
Olaf,

(We need a NodeJS installation with access to the file system).
>

How about I give you SSH access to a clean instance with Amazon Linux base
install? Will you be able to take it from there, or would you need me to
help with installing the server stack? Do you need a database?

In any case, I'll create the VPC etc. tomorrow, up to the server instance.
I'll point a subdomain of the royalesdk.org domain to it, just because I
can ;-)

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295 <06%2051952295>
I. www.ixsoftware.nl


Re: How to improve the Royale developer experience ("Smart HTML" component set)

2017-11-23 Thread Erik de Bruin
Sweet! That looks great, thanks Olaf.

Can these hang around for a while, until we're ready to give serious
thought to an WASM compatible framework?

Thanks,

EdB



On Thu, Nov 23, 2017 at 11:54 AM, Olaf Krueger  wrote:

> Hi Erik,
> I've created an example that creates a simple, editable table/datagrid.
>
> You can find the MXML pseudo code here (rows could be added by extending
> the
> data provider) [1].
> This is a working HTML/CSS3 version (static rows) [2].
>
> I think the key thing for me is to be able to use "built-in browser
> HTML/CSS3" features easier with Royale...
> maybe this is already possible with Royale and I just need more practice
> ;-)
>
> Thanks,
> Olaf
>
> [1] https://gist.github.com/ok-at-github/438ccf28800ca1db76208e6cc3a41a5c
> [2] https://codepen.io/ok-at-codepen/pen/vWjQEe
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: How to improve the Royale developer experience ("Smart HTML" component set)

2017-11-22 Thread Erik de Bruin
I like your reasoning. Can you maybe create a little MXML and AS3 project
(pseudo code, obviously) that shows what you think a 'HTML friendly
MXML/AS' file would look like?

Thanks,

EdB



On Wed, Nov 22, 2017 at 12:28 PM, Olaf Krueger  wrote:

> Hi,
> I guess you all are very busy with other stuff so sorry for introducing
> another topic here.
>
> I would like to share my experience with Royale and that said I have to
> admit that for me it is still rough to work with Royale and so I wonder
> why.
>
> This is one reason that comes to my mind:
> The Royale MXML is much different from the Flex MXML, so I can't reuse Flex
> MXML knowledge and it needs several cycles until a UI is the way I want it.
> On the other hand, the Royale MXML is also different from pure HTML. So I
> can't reuse HTML knowledge.
> Often it is easier for me to build stuff in pure CSS3/HTML than using
> Royale
> MXML.
> One reason for this is that there are tons of HTML/CSS3 snippets out there
> that solve nearly any problem.
> But we can't use this stuff directly with Royale.
>
> So I wonder how we can improve the Royale developer experience and how we
> can benefit from all these HTML/CSS3 snippets and docs out there?
> One idea that comes to my mind is that something like a "Smart HTML"
> component set could help out of this dilemma.
>
> A component set that contains/maps all HTML elements including all existing
> attributes but that is also enriched by additional smart properties (e.g.
> 'dataProvider' for an HTML table). Moreover, it should be easy to apply
> standard CSS3 to any element in the same way as it works with pure HTML
> markup.
>
> Please enlight me if something like this is already implemented or leave
> some comments if you think this makes sense... or not.  ;-)
>
> BTW: Of course, I am just talking about the HTML/JS target.
>
> Again, thanks for your time!
>
> Olaf
>
>
>
>
>
>
>
>
>
>
> --
> Sent from: http://apache-royale-development.20373.n8.nabble.com/
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

2017-11-22 Thread Erik de Bruin
> I’m 99.9% sure that browsers mark the structure as dirty when something is
> written, but none of the actual calculations and rendering happen until
> something is read or the next rendering cycle in the browser happens.
>
> I’m not sure if we’re disagreeing here.
>

We are not, just finding common ground in terms of terminology and point of
view.


> One question I have is what the performance implications are of using CSS
> vs. locally specified element styles (where the CSS does not need to be
> calculated from CSS declarations). Logically, local styling of elements
> should be more performant. I’m not sure what kinds of optimizations
> browsers have in terms of CSS lookups (and whether this is something even
> worth considering).
>

I'm pretty sure you'll be unable to measure any performance differences
between using a tag attribute (e.g. 'width') or a CSS property (e.g.
'style.width'). I would think these are simply aliases for some lower level
object field.

If you want performance optimization, I think time is better spent making
sure the most is gotten from the GCC minification and stuff like that. And,
as always, beware of premature optimization ;-)

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

2017-11-22 Thread Erik de Bruin
> > I would say that the addition of each element triggers the browser to do
> a
> > full DOM parse and reflow of the CSS.
>
> I don’t think this is true. Reflow only happens when attributes of the DOM
> is *read*. Writing to the DOM does not trigger a reflow.
>

I'm not sure I agree. An addition to the DOM means that the structure
changed and that it needs to be re-rendered. This means that in addition to
other things, at least the 'cascading' bit of CSS needs to be re-evaluated
before the browser can render the new state.

Again, I'm certainly not arguing against the RoyaleJS architecture! I was
there when it was created and stand by many of the decisions we made. I am
in this thread because Olaf's question chimed with my thinking on possible
alternative framework architectures.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

2017-11-22 Thread Erik de Bruin
> > I have no idea how the browser works internally but I thought that if we
> add
> > an HTML element to the DOM by using JS the browser has to parse it
> > afterward?
>
> I might be wrong, but I don’t think so. AFAIU, if you add elements to the
> DOM via JS, it simply gets added to the DOM tree directly. It has nothing
> to do with the DOM parser. Internally, the browser does not use the HTML
> markup. It’s just a language that the browser needs to understand to create
> the tree. Using JS bypasses the parsing step.
>

OK, terminology... The HTML parsing may be 'bypassed', but not the render
steps and I think those are triggered by each JS based DOM addition. Having
most, if not all, nodes present at page complete would certainly minimize
the number of loops, shaving off some much needed nanoseconds ;-)

I really think this is not where you want to optimize, the gains are simply
way too small. Browsers are incredibly smart rendering engines. I was just
arguing a technical point, to increase my understanding.


> > Is there a need to dive into this JS code (The part of the code that
> creates
> > and manipulates the DOM) if something went wrong? Or is it easy enough to
> > follow what's going on?
>
> I find it easy to follow. The DOM structure exists in the browser once
> it’s created, so the structure can be examined there. I think you can even
> dump the HTML markup representation of that structure if you really want.


 All major browser have a 'developer tools' window that will show you the
HTML markup as rendered. Not simply the source you put in, but the DOM the
browser is actually displaying at that time. Which includes all additions
and changes made through JS. This is actually an interesting way to debug
things, and since it doesn't depend on how the DOM is create, it works for
whatever framework is used.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Understanding Royale] Why MXML->JS->HTML instead of MXML->HTML

2017-11-22 Thread Erik de Bruin
Hi,


> 2. No need for the browser to parse HTML markup.
>

I would say that the addition of each element triggers the browser to do a
full DOM parse and reflow of the CSS. From that perspective, it might be
cheaper if the backbone HTML is defined when the page loads, instead of
being built from JS after the page load is complete. Not saying that is the
way how all the browsers do it, but simply saying that JS only might not
necessarily be the cheapest method.

3. JS lookup trees are very expensive. This is the biggest performance hit
> of using other frameworks. We avoid this by keeping direct references in
> the Royale components.

4. We don’t need to “find” elements because we already have direct
> references since the framework created them. We’re probably more performant
> than even “vanilla javascript” because we generally don’t need to even ask
> the browser to look up elements for us.
>

I guess you mean "repeated lookups"? I can't imagine other frameworks doing
document.getElementById() (or whatever sugar they use) for each object
call, that would be a way too obvious, low hanging fruit optimization. I'm
sure we don't want to publicly make these claims unless we know for sure
other networks are using very expensive lookups and RoyaleJS is way faster.

In general, I want to comment that the transpiler can basically output
whatever we want it to. That means that - if it turns out to make sense -
MXML -> HTML is possible for future frameworks. I'm working on the AS/MXML
-> WebAssembly transpiler, and I'm thinking about what framework
architecture could make the best use of WASM based logic. I think it's
worth considering everything, given that this is a chance to start another
framework from scratch.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: globalplayer.swc

2017-11-19 Thread Erik de Bruin
>
> The whole point of the feature/rename branch is to remove references to
> Flex and Flash and that includes removing dependency on both
> playerglobal.swc and airglobal.swc.
>
> My goal is that the first Royale release does not require
> playerglobal/airglobal, but you can bring it down as an optional feature.
>

Can you elaborate a bit? I'm curious how that would work, and what
(AS/MXML) features one would lose without playerglobal ;-)

How extensive a re-write are you doing for this? Is it both on the compiler
and compiler-jx?

I'm working on a branch off develop... I would hate being caught in a
massive merge conflict once your changes land. Am I better off tracking
your feature branch? How stable is that?

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


globalplayer.swc

2017-11-18 Thread Erik de Bruin
Hi,

What will happen to the globalplayer.swc distribution by Adobe when the
Flash Player is rendered obsolete in another couple of years?

Will we be allowed to distribute it ourselves?

I'm asking because the Royale compiler seems to ALWAYS need this file,
regardless of whatever framework or output you're working on. In other
words, it seems that it is a dependency of the compiler and it'd be the end
of all the compiler goodness if it stopped being available...

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [AS2WASM] Proof of concept code available

2017-11-17 Thread Erik de Bruin
Ok, I spend 'some' more time on the initial setup and managed to make it
much easier on the user. The toolchain setup is still a pain, I hope the
creators of 'wat2wasm' will start distributing binaries before we are ready
for a release. The compiler setup and building is improved and the AS
project directories should now be portable, without depending on Env vars
or complicated cli arguments...

Have a look at [1], and have fun!

Thanks,

EdB

1: https://github.com/apache/royale-asjs/wiki/User-Manual-AS2WASM



On Wed, Nov 15, 2017 at 8:24 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> Hi,
>
> As the subject suggests, I can't make up my mind about a working title for
> the WebAssembly effort.
>
> But there is also some good news: I have now assembled a usable toolchain
> to create and publish 'as2wasm' projects. As with any proof of concept,
> there are serious caveats with regard to functionality... Mostly, there is
> no actual transpiling yet ;-) But, to be fair, a week is not a lot of time
> to get that 'detail' done ;-)
>
> So, what is there to see? I have created a new, completely separate
> transpiler client (WASTC), and all the code needed to build, package and
> distribute it. It has currently one output for whatever you put in: a
> functional wasm module that exports a simple 'add' function. The client has
> a publisher that creates a viable project as output, compiling the fake
> transpiled file into a valid binary file, together with a 'glue' file to
> allow the .wasm file to load in the companion HTML file.
>
> The core of the project is a couple of NPM files. The first one is part of
> the framework and allows you to not only build the new transpiler client,
> but also to create a new project skeleton. The second one is added to each
> project skeleton and allows you to build and preview your project.
>
> If you're interested, I have created a wiki page with setup
> instructions[1]. There are a few nasty dependencies, please be patient and
> keep in mind that WebAssembly is a very young technology and the tools are
> few and far between.
>
> So: with a bit of patience you can build and "use" as2wasm as if it were
> fully functional. As long as you don't expect it to handle anything but the
> project skeleton and that there is not yet real transpilation, just a
> simple placeholder output to make everything work.
>
> If you give it a spin, keep me posted and please don't hesitate to be
> blunt and give me some (constructive) criticism.
>
> Thanks and have fun!
>
> EdB
>
> 1: https://github.com/apache/royale-asjs/wiki/User-Manual-AS2WASM
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295 <06%2051952295>
> I. www.ixsoftware.nl
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Ant Build Problem

2017-11-15 Thread Erik de Bruin
I did several fresh pulls of the repos yesterday while testing as2wasm and
I can faithfully reproduce the issue(s). I can also reliably make it go
away if I do these things:

- comment out the ant task in the 'CoreTest' target in frameworks/build.xml
- remove the 'test' dependency from the 'main' target in
frameworks/projects/Basic/build.xml

HTH,

EdB



On Thu, Nov 16, 2017 at 7:43 AM, Yishay Weiss <yishayj...@hotmail.com>
wrote:

> Thanks for the pointers Alex. Funnily I stopped getting it after playing
> around with some scripts, cleaning my changes and checking out from git the
> unit tests aren’t being run anymore and so I’m not getting it. I’ll come
> back to it when it starts itching again, but for now I can work.
>
>
>
> 
> From: Alex Harui <aha...@adobe.com.INVALID>
> Sent: Wednesday, November 15, 2017 6:41:20 PM
> To: dev@royale.apache.org
> Subject: Re: Ant Build Problem
>
> My working copies are all torn up with the refactoring and I'd prefer not
> to have to stop and build up another working copy to debug this, assuming
> I can even reproduce it.
>
> The factors are:
> -The compiler Ant tasks use ROYALE_COMPILER_HOME to find the jsc.jar to run
> -Looks like there are bugs in the scripts where ROYALE_COMPILER_HOME is
> not set by each script but maybe only the main script
> -The FlexUnit compile should be using frameworks/royale-config.xml
> -The royale-config.xml should have:
>   COMPILE::SWFAUTO
>   COMPILE::JSAUTO
> -Recent (0.8.0 and later) compilers should convert AUTO to a valid value
> for the compile.
>
>
> HTH,
> -Alex
>
> On 11/15/17, 7:48 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
> >I see the same issue! I am trying to write a quick tutorial for the new
> >wasm code, but I still can't successfully run "ant super-clean all" on
> >royale-asjs... Please help?
> >
> >compile:
> > [echo] Compiling FlexUnitRoyaleApplication.swf
> > [echo] ROYALE_HOME: /Users/erik/Desktop/tmp/royale-asjs
> > [echo] ROYALE_SWF_COMPILER_HOME: /Users/erik/Desktop/tmp/royale-asjs
> > [echo] FLEXUNIT_HOME: /Users/erik/Desktop/tmp/
> royale-asjs/in/flexunit
> > [echo] playerglobal.version: 11.1
> >[mxmlc] MXMLJSC
> >[mxmlc] -debug
> >[mxmlc] -compiler.targets=SWF
> >[mxmlc] +playerglobal.version=11.1
> >[mxmlc]
> >+env.PLAYERGLOBAL_HOME=/Users/erik/Documents/Royale/PlayerGlobal/player
> >[mxmlc]
> >-swf-library-path+=/Users/erik/Desktop/tmp/royale-asjs/frameworks/libs
> >[mxmlc]
> >-swf-library-path+=/Users/erik/Desktop/tmp/royale-asjs/
> in/flexunit/flexuni
> >t
> >[mxmlc] -define=CONFIG::dummy,false
> >[mxmlc] +royalelib=/Users/erik/Desktop/tmp/royale-asjs/frameworks/
> >[mxmlc]
> >-output=/Users/erik/Desktop/tmp/royale-asjs/frameworks/
> projects/Core/src/t
> >est/royale/FlexUnitRoyaleApplication.swf
> >[mxmlc] --
> >[mxmlc]
> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/
> projects/Core/src/test/roya
> >le/FlexUnitRoyaleApplication.mxml
> >[mxmlc] Loading configuration:
> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/royale-config.xml
> >[mxmlc]
> >[mxmlc] scanning for overrides: IFlexInfo
> >
> >
> >
> >[mxmlc] scanning for overrides: StringTrimmer
> >[mxmlc] 2.498695566 seconds
> >[mxmlc]
> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/
> projects/Core/src/test/roya
> >le/flexUnitTests/KeyboardEventConverterTest.as(23):
> >col: 5 Error: Can not resolve config constant: 'SWF'
> >[mxmlc]
> >[mxmlc] COMPILE::SWF
> >[mxmlc] ^
> >[mxmlc]
> >[mxmlc]
> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/
> projects/Core/src/test/roya
> >le/flexUnitTests/KeyboardEventConverterTest.as(56):
> >col: 13 Error: Can not resolve config constant: 'SWF'
> >[mxmlc]
> >[mxmlc] COMPILE::SWF{
> >[mxmlc] ^
> >[mxmlc]
> >[mxmlc]
> >/Users/erik/Desktop/tmp/royale-asjs/frameworks/
> projects/Core/src/test/roya
> >le/flexUnitTests/KeyboardEventConverterTest.as(68):
> >col: 13 Error: Can not resolve config constant: 'JS'
> >[mxmlc]
> >[mxmlc] COMPILE::JS{
> >[mxmlc] ^
> >[mxmlc]
> >[mxmlc]
> >/Users/erik/Desktop/tmp/royale-asjs/in/flexunit/
> flexunit/flexunit-4.2.0-20
> >140410-flex_4.12.0.swc
> >Warning: The definition mx.rpc.IResponder depended on by
> >org.flexunit.async.IAsyncTestResponder in the SWC
&

Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

2017-11-15 Thread Erik de Bruin
Carlos,

I'm seeing lot of attention this days for WebAssembly due to Safari and
> Edge supporting it.
> The expectations are high on that front and I'm reading that WASM could be
> almost ready for Spring in 2018.
> So I think this is a must for us in addition to HTML/JS/CSS effort. I'm
> trying to see the picture and even seems that both
> HTML/JS/CSS and WASM could be used at the same time right?, so in that
> case, we should think how this could be handled in Royale.
>

To help me grok the challenge of AS -> WebAssembly, I have stripped down
the transpiler to the bare minimum. This means that any tooling or
framework integration is basically excluded. The first priority must be to
get 'vanilla' AS to produce valid WAST code. At best that'll be months of
work, but seeing as I still have to learn WASM in depth, I'm sure there are
going to be some bumps in the road ;-)

I think that once there is a fair level of fidelity in the transpilation,
we can start to think about building/integrating UI frameworks with this
transpiler. I have some ideas that got snowed under when we started work on
asjs I'd like to try out. Think GCC compatible ES6 Material Design, with a
glue libraries for communication between WASM and JavaScript code.
Something like that.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


[AS2WASM] Proof of concept code available

2017-11-15 Thread Erik de Bruin
Hi,

As the subject suggests, I can't make up my mind about a working title for
the WebAssembly effort.

But there is also some good news: I have now assembled a usable toolchain
to create and publish 'as2wasm' projects. As with any proof of concept,
there are serious caveats with regard to functionality... Mostly, there is
no actual transpiling yet ;-) But, to be fair, a week is not a lot of time
to get that 'detail' done ;-)

So, what is there to see? I have created a new, completely separate
transpiler client (WASTC), and all the code needed to build, package and
distribute it. It has currently one output for whatever you put in: a
functional wasm module that exports a simple 'add' function. The client has
a publisher that creates a viable project as output, compiling the fake
transpiled file into a valid binary file, together with a 'glue' file to
allow the .wasm file to load in the companion HTML file.

The core of the project is a couple of NPM files. The first one is part of
the framework and allows you to not only build the new transpiler client,
but also to create a new project skeleton. The second one is added to each
project skeleton and allows you to build and preview your project.

If you're interested, I have created a wiki page with setup
instructions[1]. There are a few nasty dependencies, please be patient and
keep in mind that WebAssembly is a very young technology and the tools are
few and far between.

So: with a bit of patience you can build and "use" as2wasm as if it were
fully functional. As long as you don't expect it to handle anything but the
project skeleton and that there is not yet real transpilation, just a
simple placeholder output to make everything work.

If you give it a spin, keep me posted and please don't hesitate to be blunt
and give me some (constructive) criticism.

Thanks and have fun!

EdB

1: https://github.com/apache/royale-asjs/wiki/User-Manual-AS2WASM



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

2017-11-14 Thread Erik de Bruin
>
> It would be really cool if we could make the compiler understand arrow
> functions for ActionScript.
>

That would need to happen in the actual compiler
(royale-compiler/compiler). Which is basically a black box to me. I do all
my magic in the transpiler, and I barely even understand what's going on in
there ;-)

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: Add ‘glue’ utility script to allow WASM to be loaded in HTML

2017-11-14 Thread Erik de Bruin
Yes. WebAssembly only a month or so ago made it into the bleeding edge
versions of Safari and Edge, completing it's 'penetration' of the major
browsers. ES6 was there "a long time ago", so basically if we're doing
WASM, we're good on whatever JS or Web API we want to use ;-)

EdB



On Tue, Nov 14, 2017 at 10:35 PM, Harbs <harbs.li...@gmail.com> wrote:

> I’m curious about the context of this script.
>
> Will all environments where this is being run understand ES6 arrow
> functions?
>
> > On Nov 14, 2017, at 5:54 PM, erikdebr...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erikdebruin pushed a commit to branch develop
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > The following commit(s) were added to refs/heads/develop by this push:
> > new 3dc37ce  Add ‘glue’ utility script to allow WASM to be loaded in
> HTML
> > 3dc37ce is described below
> >
> > commit 3dc37ceb90c20be37639068061dba14b79e9461b
> > Author: Erik de Bruin <e...@ixsoftware.nl>
> > AuthorDate: Tue Nov 14 16:54:13 2017 +0100
> >
> >Add ‘glue’ utility script to allow WASM to be loaded in HTML
> >
> >Signed-off-by: Erik de Bruin <e...@ixsoftware.nl>
> > ---
> > .gitignore |  3 +++
> > wast/resources/glue.js | 11 +++
> > 2 files changed, 14 insertions(+)
> >
> > diff --git a/.gitignore b/.gitignore
> > index a32c5ce..64c80a8 100644
> > --- a/.gitignore
> > +++ b/.gitignore
> > @@ -141,3 +141,6 @@ vf2js/frameworks/js/
> > #FlexJS generated files
> > frameworks/js/FlexJS/generated-sources
> > manualtests/FlexJSTest_SVG/bin
> > +
> > +#WAST generated files
> > +/wast/examples/HelloWorld/bin
> > diff --git a/wast/resources/glue.js b/wast/resources/glue.js
> > new file mode 100644
> > index 000..fe66877
> > --- /dev/null
> > +++ b/wast/resources/glue.js
> > @@ -0,0 +1,11 @@
> > +function fetchAndInstantiate(url, importObject) {
> > +  return fetch(url).then(response =>
> > +response.arrayBuffer()
> > +  )
> > +  .then(bytes =>
> > +WebAssembly.instantiate(bytes, importObject)
> > +  )
> > +  .then(results =>
> > +results.instance
> > +  );
> > +}
> >
> > --
> > To stop receiving notification emails like this one, please contact
> > ['"comm...@royale.apache.org" <comm...@royale.apache.org>'].
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: Add license

2017-11-14 Thread Erik de Bruin
Just to avoid any misunderstanding: I was already working on a feature
branch (feature/wast) for the compiler stuff, and the stuff I put in
develop@royale-asjs doesn't touch any executable or build code. Also, I run
all tests before committing anything to any branch of any project, just to
make sure my commits don't break stuff.

EdB



On Tue, Nov 14, 2017 at 6:35 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
wrote:

> Erik,
>
> Agree with Alex that you wouldn't worry about all build stuff if you will
> be on separate branch. I'm just asking, we didn't have any agreement to
> have separate branch for each feature, but note thing that not only Harbs
> has currently application which is using code from develop. We are
> encourage new people to use Royale and they will use develop cause we don't
> have other option for now.
>
> Of course it is open source and you will do as you want and even if you
> break my code I will still go for a beer with you! :)
>
> Thanks for understanding! :)
> Piotr
>
>
> 2017-11-14 18:29 GMT+01:00 Alex Harui <aha...@adobe.com.invalid>:
>
> > I don't know about you, but when I'm trying something really new, I just
> > want to commit it some place so I don't lose it if my computer blows up.
> > Later, I might get to a point where I want to share it with others and
> > have them help me.  IMO, I wouldn't worry about Ant/Maven/CI until you
> > have reached that point.  Just keep on hacking...
> >
> > Looking forward to it,
> > -Alex
> >
> > On 11/14/17, 9:24 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> >
> > >>
> > >> sooner or later. The functionality which you are doing is something
> big,
> > >> that's why I'm asking to have your work on branch.
> > >>
> > >
> > >I was already working on a branch. I made two commits to
> > >develop@royale-asjs,
> > >which were in a subdirectory and completely separate from the rest of
> the
> > >framework, so I didn't see the need to create a separate branch that I'd
> > >have to maintain. But if it's easier for you to contribute to the new
> wasm
> > >target, I'll be happy to comply with your request and work on branches
> in
> > >both projects.
> > >
> > >Also, I cut out a lot of support stuff for Ant (and possibly Maven), as
> I
> > >will be using NPM to set up and run projects. However, the compiler and
> > >transpiler are building fine with a minor addition to the
> > >'compiler-jx/build.xml' Ant script, so I'm not worried about that at
> all.
> > >
> > >Thanks,
> > >
> > >EdB
> > >
> > >
> > >
> > >--
> > >Ix Multimedia Software
> > >
> > >Jan Luykenstraat 27
> > >3521 VB Utrecht
> > >
> > >T. 06-51952295
> > >I.
> > >https://na01.safelinks.protection.outlook.com/?url=
> > www.ixsoftware.nl=
> > >02%7C01%7C%7C6ef995b5c5e74f2c3dcf08d52b849efe%
> > 7Cfa7b1b5a7b34438794aed2c178
> > >decee1%7C0%7C0%7C636462770966846937=
> i6oKHqy6E66Z017y3tTDlXyL2N5eNC
> > sp
> > >EbHSxvudszM%3D=0
> >
> >
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: Add license

2017-11-14 Thread Erik de Bruin
>
> sooner or later. The functionality which you are doing is something big,
> that's why I'm asking to have your work on branch.
>

I was already working on a branch. I made two commits to develop@royale-asjs,
which were in a subdirectory and completely separate from the rest of the
framework, so I didn't see the need to create a separate branch that I'd
have to maintain. But if it's easier for you to contribute to the new wasm
target, I'll be happy to comply with your request and work on branches in
both projects.

Also, I cut out a lot of support stuff for Ant (and possibly Maven), as I
will be using NPM to set up and run projects. However, the compiler and
transpiler are building fine with a minor addition to the
'compiler-jx/build.xml' Ant script, so I'm not worried about that at all.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: Add license

2017-11-14 Thread Erik de Bruin
And I have created and published the branches you requested :-)

Thanks,

EdB



On Tue, Nov 14, 2017 at 5:16 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> Piotr,
>
> Can you explain what Maven has to do with anything? I'm pretty sure this
> will not work with Maven...
>
> Thanks,
>
> EdB
>
>
>
> On Tue, Nov 14, 2017 at 5:11 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com
> > wrote:
>
>> Erik,
>>
>> Could you create branch in repository typedefs and asjs called
>> feature/wast
>> - Once we have those three branches Maven will pickup it automatically. It
>> will be easier to me follow your changes there.
>>
>> Thanks, Piotr
>>
>>
>> 2017-11-14 16:57 GMT+01:00 <erikdebr...@apache.org>:
>>
>> > This is an automated email from the ASF dual-hosted git repository.
>> >
>> > erikdebruin pushed a commit to branch develop
>> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
>> >
>> >
>> > The following commit(s) were added to refs/heads/develop by this push:
>> >  new c469fd7  Add license
>> > c469fd7 is described below
>> >
>> > commit c469fd7401e8f9ccf75381927e0ba84db89c2de0
>> > Author: Erik de Bruin <e...@ixsoftware.nl>
>> > AuthorDate: Tue Nov 14 16:57:21 2017 +0100
>> >
>> > Add license
>> >
>> > Signed-off-by: Erik de Bruin <e...@ixsoftware.nl>
>> > ---
>> >  wast/resources/glue.js | 19 +++
>> >  1 file changed, 19 insertions(+)
>> >
>> > diff --git a/wast/resources/glue.js b/wast/resources/glue.js
>> > index fe66877..0a14ece 100644
>> > --- a/wast/resources/glue.js
>> > +++ b/wast/resources/glue.js
>> > @@ -1,3 +1,22 @@
>> > +/*
>> > + *
>> > + *  Licensed to the Apache Software Foundation (ASF) under one or more
>> > + *  contributor license agreements.  See the NOTICE file distributed
>> with
>> > + *  this work for additional information regarding copyright ownership.
>> > + *  The ASF licenses this file to You under the Apache License, Version
>> > 2.0
>> > + *  (the "License"); you may not use this file except in compliance
>> with
>> > + *  the License.  You may obtain a copy of the License at
>> > + *
>> > + *  http://www.apache.org/licenses/LICENSE-2.0
>> > + *
>> > + *  Unless required by applicable law or agreed to in writing, software
>> > + *  distributed under the License is distributed on an "AS IS" BASIS,
>> > + *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
>> > implied.
>> > + *  See the License for the specific language governing permissions and
>> > + *  limitations under the License.
>> > + *
>> > + */
>> > +
>> >  function fetchAndInstantiate(url, importObject) {
>> >return fetch(url).then(response =>
>> >  response.arrayBuffer()
>> >
>> > --
>> > To stop receiving notification emails like this one, please contact
>> > ['"comm...@royale.apache.org" <comm...@royale.apache.org>'].
>> >
>>
>>
>>
>> --
>>
>> Piotr Zarzycki
>>
>> Patreon: *https://www.patreon.com/piotrzarzycki
>> <https://www.patreon.com/piotrzarzycki>*
>>
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295 <06%2051952295>
> I. www.ixsoftware.nl
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: Add license

2017-11-14 Thread Erik de Bruin
Piotr,

Can you explain what Maven has to do with anything? I'm pretty sure this
will not work with Maven...

Thanks,

EdB



On Tue, Nov 14, 2017 at 5:11 PM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
wrote:

> Erik,
>
> Could you create branch in repository typedefs and asjs called feature/wast
> - Once we have those three branches Maven will pickup it automatically. It
> will be easier to me follow your changes there.
>
> Thanks, Piotr
>
>
> 2017-11-14 16:57 GMT+01:00 <erikdebr...@apache.org>:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erikdebruin pushed a commit to branch develop
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > The following commit(s) were added to refs/heads/develop by this push:
> >  new c469fd7  Add license
> > c469fd7 is described below
> >
> > commit c469fd7401e8f9ccf75381927e0ba84db89c2de0
> > Author: Erik de Bruin <e...@ixsoftware.nl>
> > AuthorDate: Tue Nov 14 16:57:21 2017 +0100
> >
> > Add license
> >
> > Signed-off-by: Erik de Bruin <e...@ixsoftware.nl>
> > ---
> >  wast/resources/glue.js | 19 +++
> >  1 file changed, 19 insertions(+)
> >
> > diff --git a/wast/resources/glue.js b/wast/resources/glue.js
> > index fe66877..0a14ece 100644
> > --- a/wast/resources/glue.js
> > +++ b/wast/resources/glue.js
> > @@ -1,3 +1,22 @@
> > +/*
> > + *
> > + *  Licensed to the Apache Software Foundation (ASF) under one or more
> > + *  contributor license agreements.  See the NOTICE file distributed
> with
> > + *  this work for additional information regarding copyright ownership.
> > + *  The ASF licenses this file to You under the Apache License, Version
> > 2.0
> > + *  (the "License"); you may not use this file except in compliance with
> > + *  the License.  You may obtain a copy of the License at
> > + *
> > + *  http://www.apache.org/licenses/LICENSE-2.0
> > + *
> > + *  Unless required by applicable law or agreed to in writing, software
> > + *  distributed under the License is distributed on an "AS IS" BASIS,
> > + *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > implied.
> > + *  See the License for the specific language governing permissions and
> > + *  limitations under the License.
> > + *
> > + */
> > +
> >  function fetchAndInstantiate(url, importObject) {
> >return fetch(url).then(response =>
> >  response.arrayBuffer()
> >
> > --
> > To stop receiving notification emails like this one, please contact
> > ['"comm...@royale.apache.org" <comm...@royale.apache.org>'].
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> <https://www.patreon.com/piotrzarzycki>*
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs] branch develop updated: [WAST] batch script for WASTC and an early example project

2017-11-13 Thread Erik de Bruin
My status and plans in short:

There is now a separate and independent transpiler, WASTC, (in the
'feature/wast' branch), which is addressed through the
'royale-asjs/wast/bin/wastc' script. There is no specific visitors yet for
the transpilation, so it's putting out what you put in, but hey, the
transpiler compiles and runs ;-)

Next up: complete the tool chain, mostly figure out how to automate the
'wat' (WebAssembly Text format) to 'wast' ("binary" WebAssembly format)
conversion, publish full project with HTML 'template', put up some basic
"setup and run" documentation, etc.

Then I'll get started creating the first small steps on the visitors,
getting a tiny AS application ("trace('Hello World')") to transpile to a
functioning WAST project.

>From there: complete transpiling all AS core functionality, complete the
glue script to make WAST -> JavaScript communication happen and do a bunch
of other things (including some I don't know about yet, I'm sure, because
I'm still learning WebAssembly).

I hope to have the proof of concept (everything up to 'Hello World') done
by the end of the week. Then I'll have to do some real work again :-P

Thanks,

EdB



On Mon, Nov 13, 2017 at 5:51 PM, Harbs <harbs.li...@gmail.com> wrote:

> Awesome!
>
> Does this compile yet?
>
> > On Nov 13, 2017, at 6:27 PM, erikdebr...@apache.org wrote:
> >
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erikdebruin pushed a commit to branch develop
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.git
> >
> >
> > The following commit(s) were added to refs/heads/develop by this push:
> > new e036dd3  [WAST] batch script for WASTC and an early example
> project
> > e036dd3 is described below
> >
> > commit e036dd345ba0c37b80bef09798c9c957a6088ee7
> > Author: Erik de Bruin <e...@ixsoftware.nl>
> > AuthorDate: Mon Nov 13 17:27:07 2017 +0100
> >
> >[WAST] batch script for WASTC and an early example project
> >
> >Signed-off-by: Erik de Bruin <e...@ixsoftware.nl>
> > ---
> > wast/bin/wastc | 72
> ++
> > wast/examples/HelloWorld/src/HelloWorld.as | 29 
> > 2 files changed, 101 insertions(+)
> >
> > diff --git a/wast/bin/wastc b/wast/bin/wastc
> > new file mode 100755
> > index 000..fd77d19
> > --- /dev/null
> > +++ b/wast/bin/wastc
> > @@ -0,0 +1,72 @@
> > +#!/bin/sh
> > +
> > +###
> #
> > +##
> > +##  Licensed to the Apache Software Foundation (ASF) under one or more
> > +##  contributor license agreements.  See the NOTICE file distributed
> with
> > +##  this work for additional information regarding copyright ownership.
> > +##  The ASF licenses this file to You under the Apache License, Version
> 2.0
> > +##  (the "License"); you may not use this file except in compliance with
> > +##  the License.  You may obtain a copy of the License at
> > +##
> > +##  http://www.apache.org/licenses/LICENSE-2.0
> > +##
> > +##  Unless required by applicable law or agreed to in writing, software
> > +##  distributed under the License is distributed on an "AS IS" BASIS,
> > +##  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> > +##  See the License for the specific language governing permissions and
> > +##  limitations under the License.
> > +##
> > +###
> #
> > +
> > +
> > +#
> > +# wastc shell script to launch wastc.jar on OSX, Unix, or Cygwin.
> > +#
> > +
> > +SCRIPT_HOME=`dirname "$0"`
> > +
> > +test "$FLEX_HOME" = "" && {
> > +FLEX_HOME=`dirname "$0"`/../..
> > +}
> > +
> > +for i in "$@"
> > +do
> > +case $i in
> > +-t=*|--target-player=*)
> > +TARGET_PLAYER="${i#*=}"
> > +shift
> > +;;
> > +*) # unknown option
> > +;;
> > +esac
> > +done
> > +
> > +test "$TARGET_PLAYER" = "" && {
> > +TARGET_PLAYER=11.1
> > +}
> > +
> > +case `uname` in
> > + CYGWIN*)
> > + OS="Windows"
> > + ;;
> > + *)
> > + OS=Unix
> > +esac
> > +
> > +D32=''
> > +
> > +if [ $OS = "Unix" ]; then
> > +
> 

mxmlc/asjsc command line arguments

2017-11-09 Thread Erik de Bruin
Hi,

Would someone please be so kind to tell me which command line arguments
will allow me to build a simple application from one .as file, using mxmlc
or asjsc or any of the 'straight from the compiler jars' executables, so I
can use that as a reference project/build for my new WASM compiler)?

I keep getting 'Missing builtin type Object' and similar mis-configuration
errors, but I can't for the life of me find the correct combination of
arguments... And documentation is kinda hard to find ;-)

Thanks,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Eclipse Run configuration setup

2017-11-08 Thread Erik de Bruin
>
> Unfortunately, I started the refactoring to make Flex SDK optional
> yesterday and don't really want to revert everything or set up another
> Eclipse workspace.  It will be several days until I get Eclipse working
> again, and hopefully it will make this issue go away for future Eclipse
> users.
>

I'm not in a hurry, so if you know what's going on, please take your time
fixin' it ;-)

FLEX_HOME should point to a Flex SDK, not a FlexJS/Royale SDK.  ASJS_HOME
> points to a FlexJS/Royale SDK.  It probably has to be a Royale SDK if you
> are synced up with develop branch.  See env-template.properties.
> Hopefully it is up to date after the renaming.
>

I tried all combinations of FLEX_HOME and ASJS_HOME I could think of. No
variation left me with 0 errors or failures. The errors or failures changed
over the variations, but none made it to 0.


> Also, I did not re-use old Eclipse run configs for flex-falcon after the
> rename.  I built a whole new workspace against the Royale repos.  It might
> be that the SWC tests were never run given how I set up my run configs.
>

I came back in after Flex was forked, so my workspace is "royale only." I
didn't even have a clone of the flex-sdk and flex-falcon repos until I
tried to make it work by including them this afternoon.


> IMO, we want the Royale compiler to be backward compatible as much as
> possible with compiling old Flex apps.  Maybe some code is still needed to
> fallback from royale-config.xml to flex-config.xml.  I'm pretty sure the
> code already doesn't care if the tag inside a -config.xml file is
>  or .
>

I appreciate the effort, and my comments earlier were meant as constructive
observations. The ant build are working, but I think that is because not
all test failures cause the builds to fail. The JUnit tests in Eclipse are
brutal. If not all pass, it will bug you about it ;-)

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Royale-ASJS] flexTasks

2017-11-08 Thread Erik de Bruin
Have you tried setting a FLEX_HOME environment variable? I know it's not
supposed to be needed anymore, but the past few days have taught me that
there are dark corners of the framework where it still lurks...

EdB



On Wed, Nov 8, 2017 at 3:58 PM, Peter Ent  wrote:

> I wasn't able to get the compiler to build completely, even disabling the
> tests:
>
> But I was hoping this was far enough along, so I took a chance and built
> royale-asjs which built without errors after super-clean (BTW, why is it
> wipe-all for the compiler and super-clean for asks? Be easier to remember
> if they were the same).
>
> typedef.tests:
>
> download:
>
> prepare:
>
> junit-jar-check:
>
> junit-jar:
>
> main:
>
> compile.unit.tests:
>[delete] Deleting directory
> /Users/pent/dev/royale-compiler/compiler-jx/target/test-classes
> [mkdir] Created dir:
> /Users/pent/dev/royale-compiler/compiler-jx/target/test-classes
> [javac] Compiling 87 source files to
> /Users/pent/dev/royale-compiler/compiler-jx/target/test-classes
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleAccessors.java:39: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] ((RoyaleJSProject)project).config = new
> JSGoogConfiguration();
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleClass.java:41: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] ((RoyaleJSProject)project).config = new
> JSGoogConfiguration();
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleExpressions.java:62:
> warning: [cast] redundant cast to RoyaleJSProject
> [javac] ((RoyaleJSProject)project).config = config;
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleFile.java:45: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] ((RoyaleJSProject)project).config = new
> JSGoogConfiguration();
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyalePackage.java:50: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] ((RoyaleJSProject)project).config = config;
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleProject.java:173: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac]
> ((RoyaleJSProject)project).config.
> setCompilerAllowSubclassOverrides(null
> , true);
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleProject.java:177: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] project.setTargetSettings(new
> TargetSettings(((RoyaleJSProject)project).config,
> (RoyaleJSProject)project));
> [javac]   ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleProject.java:177: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] project.setTargetSettings(new
> TargetSettings(((RoyaleJSProject)project).config,
> (RoyaleJSProject)project));
> [javac]
>  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleProject.java:196: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac]
> ((RoyaleJSProject)project).config.
> setCompilerAllowSubclassOverrides(null
> , true);
> [javac]  ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleProject.java:200: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] project.setTargetSettings(new
> TargetSettings(((RoyaleJSProject)project).config,
> (RoyaleJSProject)project));
> [javac]   ^
> [javac]
> /Users/pent/dev/royale-compiler/compiler-jx/src/test/
> java/org/apache/royale
> /compiler/internal/codegen/js/royale/TestRoyaleProject.java:200: warning:
> [cast] redundant cast to RoyaleJSProject
> [javac] project.setTargetSettings(new
> TargetSettings(((RoyaleJSProject)project).config,
> 

Re: Eclipse Run configuration setup

2017-11-08 Thread Erik de Bruin
Alex, I guess it's just you and me?

It appears some tests expect the 'old' Flex SDK in FLEX_HOME, while others
expect 'royale-asjs'. That's one thing. Another is that the SWC tests are
all failing for me, again it seems on assumptions that are no longer valid
after the fork and rename.

Thanks,

EdB



On Wed, Nov 8, 2017 at 3:28 PM, Harbs <harbs.li...@gmail.com> wrote:

> Sorry that’s above my pay grade.
>
> One day I hope to get the project setup in Eclipse and get my feet wet,
> but I’ve not gotten there yet…
>
> Good luck!
> Harbs
>
> > On Nov 8, 2017, at 1:31 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:
> >
> > Harbs,
> >
> > Are you talking about the 'ant' build succeeding or about running the
> tests
> > on the compiler project in Eclipse?
> >
> > Because the ant build succeeds even if a bunch of tests fail, while
> running
> > the tests in Eclipse will show all errors and failures.
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> >
> >
> > On Wed, Nov 8, 2017 at 11:41 AM, Harbs <harbs.li...@gmail.com> wrote:
> >
> >> You need ROYALE_HOME for the royale-asjs repo.
> >>
> >> The new environment var for the compiler is: ROYALE_COMPILER_REPO
> >>
> >> I’m pretty sure those are the only two you need.
> >>
> >> FWIW, my script to set my env vars looks like this (although much of it
> is
> >> probably no longer needed or correct).
> >>
> >> #!/bin/sh
> >>
> >> export ROYALE_COMPILER_REPO=/Users/harbs/Documents/ApacheRoyale/
> >> royale-compiler
> >> export FLEXUNIT_HOME=/Users/harbs/Documents/ApacheRoyale/flex-flexunit
> >> export FLEX_HOME=/Users/harbs/Documents/ApacheRoyale/flex-sdk
> >> export AIR_HOME=/Users/harbs/Documents/ApacheRoyale/
> >> frameworks/AIRSDK_Compiler
> >> export PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheRoyale/
> >> frameworks/libs/player
> >> export FLASHPLAYER_DEBUGGER=/Users/harbs/Documents/ApacheRoyale/
> frameworks/Flash\
> >> Player\ Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> >> export FLEXJS_HOME=/Users/harbs/Documents/ApacheRoyale/royale-asjs
> >> export FALCONJX_HOME=/Users/harbs/Documents/ApacheRoyale/royale-
> >> compiler/compiler-jx
> >> export FLEXJS_TYPEDEFS_HOME=/Users/harbs/Documents/ApacheRoyale/
> >> royale-typedefs
> >> export GOOG_HOME=/Users/harbs/Documents/ApacheRoyale/
> >> frameworks/google/closure-library
> >>
> >> export ROYALE_HOME=/Users/harbs/Documents/ApacheRoyale/royale-asjs
> >>
> >>> On Nov 8, 2017, at 12:29 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:
> >>>
> >>> Hi,
> >>>
> >>> I'm still frustrated that not all tests on compiler are passing for
> me. I
> >>> think this may revolve around the various framework builds and
> >> environment
> >>> vars...
> >>>
> >>> When I set FLEX_HOME to my asjs git repo that I have built with 'ant
> >> all',
> >>> I get a lot of errors saying:
> >>>
> >>> <
> >>> unable to open
> >>> '/Users/erik/Documents/git/royale-asjs/frameworks/libs/framework.swc'.
> >>> unable to open
> >>> '/Users/erik/Documents/git/royale-asjs/frameworks/locale/
> >> en_US/framework_rb.swc'.
> >>>>
> >>>
> >>> If I point FLEX_HOME to pre-built nightly of the asjs framework, I get
> >>> different errors:
> >>>
> >>> <
> >>> unknown configuration variable 'compiler.targets'.
> >>> /Users/erik/Documents/Royale/apache-royale-0.9.0-bin/
> >> frameworks/royale-config.xml
> >>> (line: 33)
> >>>>
> >>>
> >>> If I point FLEX_HOME to a release of the flex framework, I a lot of
> these
> >>> errors:
> >>>
> >>> <
> >>> unable to open
> >>> '/Users/erik/Documents/Royale/apache-flex-sdk-4.16.0-bin/
> >> frameworks/royale-config.xml'.
> >>>>
> >>>
> >>> What am I doing wrong? Can the folks that have all tests passing on the
> >>> 'royale-compiler/compiler' project maybe share their setup and
> settings?
> >>>
> >>> Thanks,
> >>>
> >>> EdB
> >>>
> >>>
> >>>
> >>> --
> >>> Ix Multimedia Software
> >>>
> >>> Jan Luykenstraat 27
> >>> 3521 VB Utrecht
> >>>
> >>> T. 06-51952295
> >>> I. www.ixsoftware.nl
> >>
> >>
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Eclipse Run configuration setup

2017-11-08 Thread Erik de Bruin
Harbs,

Are you talking about the 'ant' build succeeding or about running the tests
on the compiler project in Eclipse?

Because the ant build succeeds even if a bunch of tests fail, while running
the tests in Eclipse will show all errors and failures.

Thanks,

EdB





On Wed, Nov 8, 2017 at 11:41 AM, Harbs <harbs.li...@gmail.com> wrote:

> You need ROYALE_HOME for the royale-asjs repo.
>
> The new environment var for the compiler is: ROYALE_COMPILER_REPO
>
> I’m pretty sure those are the only two you need.
>
> FWIW, my script to set my env vars looks like this (although much of it is
> probably no longer needed or correct).
>
> #!/bin/sh
>
> export ROYALE_COMPILER_REPO=/Users/harbs/Documents/ApacheRoyale/
> royale-compiler
> export FLEXUNIT_HOME=/Users/harbs/Documents/ApacheRoyale/flex-flexunit
> export FLEX_HOME=/Users/harbs/Documents/ApacheRoyale/flex-sdk
> export AIR_HOME=/Users/harbs/Documents/ApacheRoyale/
> frameworks/AIRSDK_Compiler
> export PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheRoyale/
> frameworks/libs/player
> export 
> FLASHPLAYER_DEBUGGER=/Users/harbs/Documents/ApacheRoyale/frameworks/Flash\
> Player\ Debugger.app/Contents/MacOS/Flash\ Player\ Debugger
> export FLEXJS_HOME=/Users/harbs/Documents/ApacheRoyale/royale-asjs
> export FALCONJX_HOME=/Users/harbs/Documents/ApacheRoyale/royale-
> compiler/compiler-jx
> export FLEXJS_TYPEDEFS_HOME=/Users/harbs/Documents/ApacheRoyale/
> royale-typedefs
> export GOOG_HOME=/Users/harbs/Documents/ApacheRoyale/
> frameworks/google/closure-library
>
> export ROYALE_HOME=/Users/harbs/Documents/ApacheRoyale/royale-asjs
>
> > On Nov 8, 2017, at 12:29 PM, Erik de Bruin <e...@ixsoftware.nl> wrote:
> >
> > Hi,
> >
> > I'm still frustrated that not all tests on compiler are passing for me. I
> > think this may revolve around the various framework builds and
> environment
> > vars...
> >
> > When I set FLEX_HOME to my asjs git repo that I have built with 'ant
> all',
> > I get a lot of errors saying:
> >
> > <
> > unable to open
> > '/Users/erik/Documents/git/royale-asjs/frameworks/libs/framework.swc'.
> > unable to open
> > '/Users/erik/Documents/git/royale-asjs/frameworks/locale/
> en_US/framework_rb.swc'.
> >>
> >
> > If I point FLEX_HOME to pre-built nightly of the asjs framework, I get
> > different errors:
> >
> > <
> > unknown configuration variable 'compiler.targets'.
> > /Users/erik/Documents/Royale/apache-royale-0.9.0-bin/
> frameworks/royale-config.xml
> > (line: 33)
> >>
> >
> > If I point FLEX_HOME to a release of the flex framework, I a lot of these
> > errors:
> >
> > <
> > unable to open
> > '/Users/erik/Documents/Royale/apache-flex-sdk-4.16.0-bin/
> frameworks/royale-config.xml'.
> >>
> >
> > What am I doing wrong? Can the folks that have all tests passing on the
> > 'royale-compiler/compiler' project maybe share their setup and settings?
> >
> > Thanks,
> >
> > EdB
> >
> >
> >
> > --
> > Ix Multimedia Software
> >
> > Jan Luykenstraat 27
> > 3521 VB Utrecht
> >
> > T. 06-51952295
> > I. www.ixsoftware.nl
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Royale-ASJS] flexTasks

2017-11-08 Thread Erik de Bruin
Disabling the tests that run FlexUnitRoyaleApplication.swf allow the build
to succeed.


> Shooting in the dark here: FlexUnit has some dependencies on flex. Do you
> have flex-sdk downloaded?
>

This brings me to a second question, which I'll raise in a new thread to
keep this one to the point.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Royale-ASJS] flexTasks

2017-11-08 Thread Erik de Bruin
An addition: running
'frameworks/projects/Basic/src/test/royale/flexUnitTests/FlexUnitRoyaleApplication.swf'
starts out with this error: "VerifyError: Error #1014: Class IResponder
could not be found." to then proceed to the error I mentioned earlier...

Thanks,

EdB



On Wed, Nov 8, 2017 at 10:37 AM, Erik de Bruin <e...@ixsoftware.nl> wrote:

> Having some problems with setup as well...
>
> When I follow the clean and rebuild instructions everything is fine until
> ant on 'royale-asjs' hits an error in one of the apps: "ReferenceError:
> Error #1065: Variable FlexUnitRoyaleApplication is not defined." and the
> build times out.
>
> This is the cli output at the point of failure:
>
> <
> test:
> [mkdir] Created dir: /Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/royale/out
>  [flexunit] Validating task attributes ...
>  [flexunit] Generating default values ...
>  [flexunit] Using the following settings for the test run:
>  [flexunit] haltonfailure: [false]
>  [flexunit] headless: [false]
>  [flexunit] display: [99]
>  [flexunit] localTrusted: [true]
>  [flexunit] player: [flash]
>  [flexunit] port: [1024]
>  [flexunit] swf: [/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/royale/FlexUnitRoyaleApplication.swf]
>  [flexunit] timeout: [9ms]
>  [flexunit] toDir: [/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/royale/out]
>  [flexunit] Setting up server process ...
>  [flexunit] Starting server ...
>  [flexunit] Opening server socket on port [1024].
>  [flexunit] Waiting for client connection ...
>  [flexunit] Entry [/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/royale] already available in local trust file at
> [/Users/erik/Library/Preferences/Macromedia/Flash Player/#Security/
> FlashPlayerTrust/flexUnit.cfg].
>  [flexunit] Executing 'open' with arguments:
>  [flexunit] '/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Basic/src/test/royale/FlexUnitRoyaleApplication.swf'
>  [flexunit]
>  [flexunit] The ' characters around the executable and arguments are
>  [flexunit] not part of the command.
>  [flexunit]
>  [flexunit]
>  [flexunit] Stopping server ...
>  [flexunit] End of test data reached, sending acknowledgement to player ...
>  [flexunit] Closing client connection ...
>  [flexunit] Closing server on port [1024] ...
> >
>
> Ideas?
>
> Thanks,
>
> EdB
>
>
>
> On Wed, Nov 8, 2017 at 6:31 AM, Alex Harui <aha...@adobe.com.invalid>
> wrote:
>
>> Sync all 3 repos, start with royale-compiler, then royale-typedefs, then
>> royale-asjs.
>>
>> I'd recommend running "ant wipe-all" in royale-compiler before running
>> just "ant" (which now builds everything in royale-compiler).  And in
>> royale-asjs, run "ant super-clean" before running "ant".
>>
>> HTH,
>> -Alex
>>
>> On 11/7/17, 1:34 PM, "Peter Ent" <p...@adobe.com.INVALID> wrote:
>>
>> >I sync'd the repo (develop branch) and rebuilt asjs. I'm seeing this
>> >notice:
>> >
>> >Could not load definitions from resource flexTasks.tasks. It could not be
>> >found.
>> >
>> >Wouldn't "flexTasks.tasks" get renamed to "royaleTasks.tasks" ?
>> >
>> >—peter
>>
>>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295 <06%2051952295>
> I. www.ixsoftware.nl
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [Royale-ASJS] flexTasks

2017-11-08 Thread Erik de Bruin
Having some problems with setup as well...

When I follow the clean and rebuild instructions everything is fine until
ant on 'royale-asjs' hits an error in one of the apps: "ReferenceError:
Error #1065: Variable FlexUnitRoyaleApplication is not defined." and the
build times out.

This is the cli output at the point of failure:

<
test:
[mkdir] Created dir:
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/out
 [flexunit] Validating task attributes ...
 [flexunit] Generating default values ...
 [flexunit] Using the following settings for the test run:
 [flexunit] haltonfailure: [false]
 [flexunit] headless: [false]
 [flexunit] display: [99]
 [flexunit] localTrusted: [true]
 [flexunit] player: [flash]
 [flexunit] port: [1024]
 [flexunit] swf:
[/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/FlexUnitRoyaleApplication.swf]
 [flexunit] timeout: [9ms]
 [flexunit] toDir:
[/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/out]
 [flexunit] Setting up server process ...
 [flexunit] Starting server ...
 [flexunit] Opening server socket on port [1024].
 [flexunit] Waiting for client connection ...
 [flexunit] Entry
[/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale]
already available in local trust file at
[/Users/erik/Library/Preferences/Macromedia/Flash
Player/#Security/FlashPlayerTrust/flexUnit.cfg].
 [flexunit] Executing 'open' with arguments:
 [flexunit]
'/Users/erik/Documents/git/royale-asjs/frameworks/projects/Basic/src/test/royale/FlexUnitRoyaleApplication.swf'
 [flexunit]
 [flexunit] The ' characters around the executable and arguments are
 [flexunit] not part of the command.
 [flexunit]
 [flexunit]
 [flexunit] Stopping server ...
 [flexunit] End of test data reached, sending acknowledgement to player ...
 [flexunit] Closing client connection ...
 [flexunit] Closing server on port [1024] ...
>

Ideas?

Thanks,

EdB



On Wed, Nov 8, 2017 at 6:31 AM, Alex Harui  wrote:

> Sync all 3 repos, start with royale-compiler, then royale-typedefs, then
> royale-asjs.
>
> I'd recommend running "ant wipe-all" in royale-compiler before running
> just "ant" (which now builds everything in royale-compiler).  And in
> royale-asjs, run "ant super-clean" before running "ant".
>
> HTH,
> -Alex
>
> On 11/7/17, 1:34 PM, "Peter Ent"  wrote:
>
> >I sync'd the repo (develop branch) and rebuilt asjs. I'm seeing this
> >notice:
> >
> >Could not load definitions from resource flexTasks.tasks. It could not be
> >found.
> >
> >Wouldn't "flexTasks.tasks" get renamed to "royaleTasks.tasks" ?
> >
> >—peter
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-compiler] branch wast created (now e336021)

2017-11-07 Thread Erik de Bruin
I moved it.

I know nothing about Maven, and I won't be investing time in writing code
to support it: that'll have to be another volunteer's challenge ;-)

EdB



On Tue, Nov 7, 2017 at 5:24 PM, Piotr Zarzycki 
wrote:

> Hi Erik,
>
> Could you please create that branch under "feature/" folder -
> "feature/wast" - Thanks to that Maven build automatically pickup all your
> changes if we create branches for other repository as well.
>
> Thanks, Piotr
>
>
> 2017-11-07 15:13 GMT+01:00 :
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erikdebruin pushed a change to branch wast
> > in repository https://gitbox.apache.org/repos/asf/royale-compiler.git.
> >
> >
> >   at e336021  Get first test to run to completion on WAST configured
> > code; test fails -> must create emitters
> >
> > This branch includes the following new commits:
> >
> >  new e336021  Get first test to run to completion on WAST configured
> > code; test fails -> must create emitters
> >
> > The 1 revisions listed above as "new" are entirely new to this
> > repository and will be described in separate emails.  The revisions
> > listed as "add" were already present in the repository and have only
> > been added to this reference.
> >
> >
> > --
> > To stop receiving notification emails like this one, please contact
> > ['"comm...@royale.apache.org" '].
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> Patreon: *https://www.patreon.com/piotrzarzycki
> *
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Compiler projects setup and tests

2017-11-06 Thread Erik de Bruin
I'll give it another look tomorrow. Don't care all that much about the
'compiler' failures (yet), and the 'compiler-jx' failures appear to be true
failures, where expected values don't match the actual values.

I'm planning on taking the first steps towards as/mxml to WebAssembly
(wasm) in the coming days. It's going to be an interesting walk ;-)

EdB



On Mon, Nov 6, 2017 at 6:31 PM, Alex Harui <aha...@adobe.com.invalid> wrote:

> The tests all pass for me.  Again, I am in the process of refactoring all
> of these tests so they don't have dependencies on flex or royale framework
> code (or Flash/AIR either).  Then hopefully it will be easier to get up
> and running.
>
> -Alex
>
> On 11/6/17, 7:06 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
> >Hi,
> >
> >I just spent the day wrestling with the setup of the compiler projects in
> >Eclipse. It's been a while, so it took some doing to get most of the tests
> >to run and pass on 'compiler' and 'compiler-js'.
> >
> >A question for the current compiler hackers: do all tests on 'compiler'
> >and
> >'compiler-js' pass for you? I have 105 failures on 'compiler', and 2
> >failures on 'compiler-jx'.
> >
> >An observation: when I try to run 'ant all' on 'royale-asjs', it fails
> >with
> >this error:
> >
> ><
> >CoreTest:
> >
> >check-for-tests:
> >
> >check-falcon-home:
> >
> >check-falconjx-home:
> >
> >check-compiler:
> >
> >test:
> >
> >clean:
> >
> >compile:
> > [echo] Compiling FlexUnitRoyaleApplication.swf
> > [echo] FLEX_HOME: /Users/erik/Documents/git/royale-asjs
> > [echo] FALCON_HOME: /Users/erik/Documents/git/royale-asjs
> > [echo] FLEXUNIT_HOME:
> >/Users/erik/Documents/git/royale-asjs/in/flexunit
> > [echo] playerglobal.version: 11.1
> >[mxmlc] MXMLJSC
> >[mxmlc] -debug
> >[mxmlc] -compiler.targets=SWF
> >[mxmlc] +playerglobal.version=11.1
> >[mxmlc]
> >+env.PLAYERGLOBAL_HOME=/Users/erik/Documents/Royale/PlayerGlobal/player
> >[mxmlc]
> >-swf-library-path+=/Users/erik/Documents/git/royale-asjs/frameworks/libs
> >[mxmlc]
> >-swf-library-path+=/Users/erik/Documents/git/royale-
> asjs/in/flexunit/flexu
> >nit
> >[mxmlc] -define=CONFIG::dummy,false
> >[mxmlc] +royalelib=/Users/erik/Documents/git/royale-asjs/frameworks/
> >[mxmlc]
> >-output=/Users/erik/Documents/git/royale-asjs/
> frameworks/projects/Core/src
> >/test/royale/FlexUnitRoyaleApplication.swf
> >[mxmlc] --
> >[mxmlc]
> >/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Core/src/test/ro
> >yale/FlexUnitRoyaleApplication.mxml
> >[mxmlc] Loading configuration:
> >/Users/erik/Documents/git/royale-asjs/frameworks/royale-config.xml
> >[mxmlc]
> >[mxmlc] 1.10459097 seconds
> >[mxmlc]
> >/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Core/src/test/ro
> >yale/FlexUnitRoyaleApplication.mxml(21):
> >col: 1 Error: This tag could not be resolved to an ActionScript class. It
> >will be ignored.
> >[mxmlc]
> >[mxmlc]  >xmlns:fx="https://na01.safelinks.protection.outlook.
> com/?url=http%3A%2F%2F
> >ns.adobe.com%2Fmxml%2F2009=02%7C01%7C%7C87826518cf114acd2ae008d52528
> 1
> >4ee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636455776432534322=
> >MkDea%2FIaLCHSp74w08YEskMBKNalDsaF8u1a61kqmSM%3D=0"
> >[mxmlc] ^
> >[mxmlc]
> >[mxmlc]
> >/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Core/src/test/ro
> >yale/FlexUnitRoyaleApplication.mxml(21):
> >col: 1 Error: This tag could not be resolved to an ActionScript class. It
> >will be ignored.
> >[mxmlc]
> >[mxmlc]  >xmlns:fx="https://na01.safelinks.protection.outlook.
> com/?url=http%3A%2F%2F
> >ns.adobe.com%2Fmxml%2F2009=02%7C01%7C%7C87826518cf114acd2ae008d52528
> 1
> >4ee%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636455776432534322=
> >MkDea%2FIaLCHSp74w08YEskMBKNalDsaF8u1a61kqmSM%3D=0"
> >[mxmlc] ^
> >[mxmlc]
> >
> >test:
> >[mkdir] Created dir:
> >/Users/erik/Documents/git/royale-asjs/frameworks/
> projects/Core/src/test/ro
> >yale/out
> > [flexunit] Validating task attributes ...
> >
> >BUILD FAILED
> >/Users/erik/Documents/git/royale-asjs/build.xml:563: The following error
> >occurred while executing this line:
> >/Users/erik/Documents/git/royale-asjs/frameworks/build.xml:118: The
> >following error occurr

Compiler projects setup and tests

2017-11-06 Thread Erik de Bruin
Hi,

I just spent the day wrestling with the setup of the compiler projects in
Eclipse. It's been a while, so it took some doing to get most of the tests
to run and pass on 'compiler' and 'compiler-js'.

A question for the current compiler hackers: do all tests on 'compiler' and
'compiler-js' pass for you? I have 105 failures on 'compiler', and 2
failures on 'compiler-jx'.

An observation: when I try to run 'ant all' on 'royale-asjs', it fails with
this error:

<
CoreTest:

check-for-tests:

check-falcon-home:

check-falconjx-home:

check-compiler:

test:

clean:

compile:
 [echo] Compiling FlexUnitRoyaleApplication.swf
 [echo] FLEX_HOME: /Users/erik/Documents/git/royale-asjs
 [echo] FALCON_HOME: /Users/erik/Documents/git/royale-asjs
 [echo] FLEXUNIT_HOME: /Users/erik/Documents/git/royale-asjs/in/flexunit
 [echo] playerglobal.version: 11.1
[mxmlc] MXMLJSC
[mxmlc] -debug
[mxmlc] -compiler.targets=SWF
[mxmlc] +playerglobal.version=11.1
[mxmlc]
+env.PLAYERGLOBAL_HOME=/Users/erik/Documents/Royale/PlayerGlobal/player
[mxmlc]
-swf-library-path+=/Users/erik/Documents/git/royale-asjs/frameworks/libs
[mxmlc]
-swf-library-path+=/Users/erik/Documents/git/royale-asjs/in/flexunit/flexunit
[mxmlc] -define=CONFIG::dummy,false
[mxmlc] +royalelib=/Users/erik/Documents/git/royale-asjs/frameworks/
[mxmlc]
-output=/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/src/test/royale/FlexUnitRoyaleApplication.swf
[mxmlc] --
[mxmlc]
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/src/test/royale/FlexUnitRoyaleApplication.mxml
[mxmlc] Loading configuration:
/Users/erik/Documents/git/royale-asjs/frameworks/royale-config.xml
[mxmlc]
[mxmlc] 1.10459097 seconds
[mxmlc]
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/src/test/royale/FlexUnitRoyaleApplication.mxml(21):
col: 1 Error: This tag could not be resolved to an ActionScript class. It
will be ignored.
[mxmlc]
[mxmlc] http://ns.adobe.com/mxml/2009;
[mxmlc] ^
[mxmlc]
[mxmlc]
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/src/test/royale/FlexUnitRoyaleApplication.mxml(21):
col: 1 Error: This tag could not be resolved to an ActionScript class. It
will be ignored.
[mxmlc]
[mxmlc] http://ns.adobe.com/mxml/2009;
[mxmlc] ^
[mxmlc]

test:
[mkdir] Created dir:
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/src/test/royale/out
 [flexunit] Validating task attributes ...

BUILD FAILED
/Users/erik/Documents/git/royale-asjs/build.xml:563: The following error
occurred while executing this line:
/Users/erik/Documents/git/royale-asjs/frameworks/build.xml:118: The
following error occurred while executing this line:
/Users/erik/Documents/git/royale-asjs/frameworks/build.xml:233: The
following error occurred while executing this line:
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/build.xml:56:
The following error occurred while executing this line:
/Users/erik/Documents/git/royale-asjs/frameworks/projects/Core/src/test/royale/build.xml:141:
The provided 'swf' property value [] could not be found or is not a valid
remote URL.
>

Is it me, or is something not completely "done" after the fork/rename?

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: [royale-asjs.wiki] branch master updated: Give it a bit more body

2017-10-03 Thread Erik de Bruin
Work in progress, just collecting steps and trying to get to terms with git
-> GitHub Wiki -> MarkDown quicks :-)

My idea is to have a general landing page and then a selection of IDEs as a
submenu, with separate quick start steps for each.

I will take care of the VSCode steps, others can fill in for other IDEs.

EdB



On Tue, Oct 3, 2017 at 11:46 AM, Piotr Zarzycki <piotrzarzyck...@gmail.com>
wrote:

> Hi Erik,
>
> Since your quick start is how to use VSCode with Royale I believe you
> should also change title which states about that. We have also Moonshine
> where Quick start will look very different.
>
> Piotr
>
>
> 2017-10-03 11:22 GMT+02:00 <erikdebr...@apache.org>:
>
> > This is an automated email from the ASF dual-hosted git repository.
> >
> > erikdebruin pushed a commit to branch master
> > in repository https://gitbox.apache.org/repos/asf/royale-asjs.wiki.git
> >
> >
> > The following commit(s) were added to refs/heads/master by this push:
> >  new 456a558  Give it a bit more body
> > 456a558 is described below
> >
> > commit 456a5584140dd707e68eec61649d48a9042bf275
> > Author: Erik de Bruin <e...@ixsoftware.nl>
> > AuthorDate: Tue Oct 3 11:22:42 2017 +0200
> >
> > Give it a bit more body
> >
> > Signed-off-by: Erik de Bruin <e...@ixsoftware.nl>
> > ---
> >  Quick-Start.md | 54 ++
> > 
> >  1 file changed, 50 insertions(+), 4 deletions(-)
> >
> > diff --git a/Quick-Start.md b/Quick-Start.md
> > index f4d1dce..5c0ff7d 100644
> > --- a/Quick-Start.md
> > +++ b/Quick-Start.md
> > @@ -1,7 +1,53 @@
> > -1) Set prerequisites; get and build source ([Project README](
> > https://github.com/apache/royale-asjs))
> > +- Set prerequisites; get and build source ([Project README](
> > https://github.com/apache/royale-asjs))
> >
> > -2) Download and install Visual Studio Code
> > +- Download and install [Visual Studio Code](https://code.
> > visualstudio.com/)
> >
> > -3) Do more stuff
> > +- Install Josh Tynjala's [asconfigc](https://www.npmjs.
> > com/package/asconfigc), a command line utility for compiling AS/MXML
> > projects
> >
> > -4) Test editing using GitHub Wiki edit tool
> > +- Install the [AS/MXML VSCode Extension](https://
> nextgenactionscript.com)
> > by the same author
> > +
> > +- Select a workspace in VSCode
> > +
> > +- Select SDK for workspace
> > +
> > +- Set up project:
> > +
> > +  project
> > +  |
> > +  + -- src
> > +  ||
> > +  |\ -- HelloFlexJS.mxml
> > +  |
> > +  + -- asconfig.json
> > +
> > +  - in '*asconfig.json*':
> > +
> > +```json
> > +{
> > +   "compilerOptions": {
> > +   "targets": [
> > +   "JSFlex"
> > +   ]
> > +   },
> > +   "files": [
> > +   "src/HelloFlexJS.mxml"
> > +   ]
> > +}
> > +```
> > +
> > +  - in '*src/HelloFlexJS.mxml*'
> > +
> > +```xml
> > +
> > +http://ns.adobe.com/mxml/2009;
> > xmlns:js="library://ns.apache.org/flexjs/express">
> > +   
> > +   
> > +   
> > +   
> > +   
> > +
> > +```
> > +
> > +- Select the Debug panel in VSCode and hit the green arrow ('run') to
> > build and run the application.
> > +
> > +- Hello World!
> >
> > --
> > To stop receiving notification emails like this one, please contact
> > ['"comm...@royale.apache.org" <comm...@royale.apache.org>'].
> >
>
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> <https://pl.linkedin.com/in/piotr-zarzycki-92a53552>
>
> GitHub: https://github.com/piotrzarzycki21
>



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Github Pages (was Re: Github wikis)

2017-10-03 Thread Erik de Bruin
Hi,

I started work on a Quick Start guide [1] to bridge the gap between the
README (source setup and build) and any in-depth documentation.

It will simply be the steps I took to get a project compiling on my
machine. I had to gather the information from various places and I thought
it'd be nice if other newbies like me didn't have to dig as deep, but could
set up and execute their local dev installation in a reasonable amount of
time.

EdB

1: https://github.com/apache/royale-asjs/wiki



On Tue, Oct 3, 2017 at 10:07 AM, Piotr Zarzycki 
wrote:

> Hi Alex,
>
> +1 for royale-docs. If I would like to make something like Olaf [1] started
> and move all his already gathered information in that structure where in
> your opinion guys should it go ? Into the royale-docs as gh pages or into
> royale-asjs as Wiki ?
>
> Does anyone is against to have it Olaf's work as an starting point ?
>
> [1] https://github.com/ok-at-github/flexjs-docs/wiki
>
> Thanks,
> Piotr
>
>
> 2017-10-03 9:55 GMT+02:00 Harbs :
>
> > royale-docs is good.
> >
> > > On Oct 3, 2017, at 9:36 AM, OmPrakash Muppirala 
> > wrote:
> > >
> > > I prefer royale-docs
> > >
> > > Thanks,
> > > Om
> > >
> > > On Oct 2, 2017 11:04 PM, "Alex Harui" 
> wrote:
> > >
> > >> Per Infra:  "Pages are not enabled until we have some content to point
> > to.
> > >> Best thing I think is to create a new royale-pages repository (or
> > whatever
> > >> name) and I'll enable it on that - ensure some content in 'master'
> > branch
> > >> or 'master/docs' . those pages would then be available on
> > >> apache.github.io/royale-pages (or whatever)"
> > >>
> > >> Shall we create a royale-pages repo?  Anybody think it should have
> some
> > >> other name?  "royale-documentation"?  I think it will hold our
> non-ASDoc
> > >> user documentation.
> > >>
> > >> Thoughts?
> > >> -Alex
> > >>
> > >> On 10/2/17, 11:42 AM, "Alex Harui"  wrote:
> > >>
> > >>> I think I learned that Github Pages is not per-repo, it is one per
> > Apache
> > >>> Project.
> > >>>
> > >>> It is a bit easier to have one repo per release product.  Combining
> > repos
> > >>> for a release is a bit of extra work.  There should be examples in
> the
> > >>> IDE-friendly artifact.  IMO, TourJS would have its own release
> > schedule.
> > >>>
> > >>> My 2 cents,
> > >>> -Alex
> > >>>
> > >>> On 10/2/17, 11:32 AM, "Harbs"  wrote:
> > >>>
> >  I’d like to setup an example repo so it’ll build a website (i.e.
> > Github
> >  Pages) where the samples could be run. It seems similar to tourjs
> in a
> >  way, but different. “Examples” to me is more like a tutorial on how
> to
> >  use Royale while tourjs is more of a reference of the components.
> They
> >  seem separate and complimentary.
> > 
> >  Harbs
> > 
> > 
> > > On Oct 2, 2017, at 9:25 PM, Peter Ent 
> > wrote:
> > >
> > > I have been thinking that examples should be moved from royale-asjs
> > and
> > > put into its own royals-examples repo and then a wiki for that
> would
> > > work
> > > well.
> > >
> > > Maybe the tourjs should be a subdirectory in examples.
> > >
> > > ‹peter
> > >
> > > On 10/2/17, 2:14 PM, "Harbs"  wrote:
> > >
> > >> INFRA just informed us that Github Wikis are now an option and
> they
> > >> want
> > >> to know which repos we want wikis for.[1]
> > >>
> > >> royale-asjs and royale-compiler seem like no-brainers.
> > >>
> > >> What about royale-typedefs, royale-tourjs and royale-website? Does
> > >> anyone
> > >> see a reason for a wiki in those?
> > >>
> > >> At what point do folks think we should set up an ³examples² repo?
> A
> > >> wiki
> > >> would probably be appropriate on something like that.
> > >>
> > >> Thanks,
> > >> Harbs
> > >>
> > >>
> > >> [1]https://na01.safelinks.protection.outlook.com/?url=
> > >> https%3A%2F%2Fiss
> > >> u
> > >> es
> > >>
> > >> .apache.org%2Fjira%2Fbrowse%2FINFRA-15138%
> > >> 3FfocusedCommentId%3D16188401
> > >> %
> > >> 26
> > >>
> > >> page%3Dcom.atlassian.jira.plugin.system.issuetabpanels%
> > >> 3Acomment-tabpan
> > >> e
> > >> l%
> > >>
> > >> 23comment-16188401=02%7C01%7C%7Cf13e83a4f7594535bec608d509c1
> > >> 76d8%7
> > >> C
> > >> fa
> > >>
> > >> 7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636425648884686688&
> > >> sdata=%2FSB
> > >> h
> > >> %2
> > >> BpyjIfrx%2FcwnFZAxqD%2FGdT3lvte6%2FWItPQDTIqs%3D=0
> > >
> > 
> > >>>
> > >>
> > >>
> >
> >
>
>
> --
>
> Piotr Zarzycki
>
> mobile: +48 880 859 557
> skype: zarzycki10
>
> LinkedIn: http://www.linkedin.com/piotrzarzycki
> 
>
> GitHub: 

Re: [DISCUSS] project vs. product name vs artifact names

2017-10-02 Thread Erik de Bruin
>
> So our mantra should be "keep it simple" to be able to make people outside
> our world have the opportunity to be attracted by our tech.
>

Agreed on the "simple." But it may be better to have a few products that do
what they advertise to do instead of one monolithic product that I then
need to configure the heck out of to make it do what I want... And trust
me, as the "new" guy coming in, I can tell you from the past few days of
trying: it's already overwhelming when you try to get into Royale.

I'd rather have a few product preconfigured and ready to compile to my
intended output format out of the box, than one large one that I then have
to look up in the manual to see if I can find a combination of settings and
compiler configs to tame it.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Build failed in Jenkins: royale-asjs #7

2017-09-29 Thread Erik de Bruin
I can't imagine that changes to the README caused the build to fail, but
I've been doing this long enough not to rule anything out... :-)

Also, the 'reply-to' address on the failure email is still
d...@flex.apache.org.

EdB



On Fri, Sep 29, 2017 at 2:35 PM,  wrote:

> See 
>
> Changes:
>
> [erik] A bit of a rewrite
>
> [erik] Add .md to make GitHub render the MarkDown
>
> [erik] Pre-final version, committing to check on GitHub
>
> --
> [...truncated 9550 lines...]
> [javac]^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestStep
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/TestStep.java>:87: error:
> cannot find symbol
> [javac] protected WebDriver webDriver;
> [javac]   ^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestStep
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/TestCase.java>:142: error:
> cannot find symbol
> [javac] public boolean runTest(WebDriver webDriver)
> [javac]^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestCase
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/TestCase.java>:152: error:
> cannot find symbol
> [javac] private boolean runSetup(WebDriver webDriver)
> [javac]  ^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestCase
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/TestCase.java>:174: error:
> cannot find symbol
> [javac] private boolean runBody(WebDriver webDriver)
> [javac] ^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestCase
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/TestCase.java>:196: error:
> cannot find symbol
> [javac] private boolean runCleanup(WebDriver webDriver)
> [javac]^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestCase
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/TestCase.java>:238: error:
> cannot find symbol
> [javac] private boolean runSteps(WebDriver webDriver)
> [javac]  ^
> [javac]   symbol:   class WebDriver
> [javac]   location: class TestCase
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchKeyEvent.java>:25:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.JavascriptExecutor;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchKeyEvent.java>:26:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.Keys;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchKeyEvent.java>:27:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.WebDriver;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchKeyEvent.java>:28:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.WebElement;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchMouseClickEvent.java>:23:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.JavascriptExecutor;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchMouseClickEvent.java>:24:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.WebDriver;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchMouseClickEvent.java>:25:
> error: package org.openqa.selenium does not exist
> [javac] import org.openqa.selenium.WebElement;
> [javac]   ^
> [javac]  asjs/ws/mustella/src/main/java/marmotinni/DispatchMouseEvent.java>:23:
> error: 

Re: Failed build doing 'ant all' on the packaging branch

2017-09-29 Thread Erik de Bruin
>
> I will also rewrite the READme a bit to make the procedure clearer, and
> convert it to MarkDown to make it look good on GitHub.
>

I have finished my version of the READme. I renamed it to README.md to get
GitHub to render the MarkDown.

You can check it out on GitHub:

https://github.com/apache/royale-asjs/tree/packaging

Thanks,

EdB


Failed build doing 'ant all' on the packaging branch

2017-09-29 Thread Erik de Bruin
Hi,

Currently, when I do an 'ant all' on the packaging branch, with just
JAVA_HOME and ANT_HOME set, I get a failed build.

[Error]
BUILD FAILED
/Users/erik/Desktop/royale/royale-asjs/build.xml:1545: The following error
occurred while executing this line:
/Users/erik/Desktop/royale/royale-asjs/build.xml:1618: The following error
occurred while executing this line:
/Users/erik/Desktop/royale/royale-compiler/build.xml:107: The following
error occurred while executing this line:
/Users/erik/Desktop/royale/royale-compiler/compiler/build.xml:711: The
following error occurred while executing this line:
/Users/erik/Desktop/royale/royale-compiler/compiler/src/test/build.xml:279:
Tests failed
[/Error]

Turns out that you do need to set PLAYERGLOBAL_HOME and
FLASHPLAYER_DEBUGGER, otherwise some of the tests on royale-compiler fail.
I'll make adjustments to the READme to reflect this.

I will also rewrite the READme a bit to make the procedure clearer, and
convert it to MarkDown to make it look good on GitHub.

Thanks,

EdB


Re: FALCON_HOME and FALCONJX_HOME

2017-09-29 Thread Erik de Bruin
I'm talking about getting the source on my system such that it will build
and I can work on it.

I am starting a separate thread on the issues I'm finding.

Thanks,

EdB



On Fri, Sep 29, 2017 at 9:14 AM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> Hi Erik,
>
> Not sure what you mean by "install".  I was only focused on getting the
> repos set up on someone's computer to make changes and push them.  I
> haven't put in much documentation of the IDE-friendly packaging which I
> think we should use that doesn't use the Apache Flex SDK Installer.
> Instead you will be able to unzip a package and use it if you don't need
> SWF support.
>
> I will tackle that tomorrow.
>
> Later,
> -Alex
>
> On 9/29/17, 12:03 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
> >Alex,
> >
> >I'm going in today in a second attempt to do a clean install, and will
> >change/add code and documentation I find missing.
> >
> >EdB
> >
> >
> >
> >On Fri, Sep 29, 2017 at 8:13 AM, Alex Harui <aha...@adobe.com.invalid>
> >wrote:
> >
> >> OK, I have "ant all" working in royale-asjs and tried to describe how to
> >> set it up in READme.  Please use the packaging branch in royale-asjs.  I
> >> could just merge this into develop since the develop branch probably
> >>won't
> >> work as it currently is, or we can put more polish on the packaging in
> >>the
> >> packaging branch first.
> >>
> >> Please give it a try and let us know what the result is.
> >>
> >> Thanks,
> >> -Alex
> >>
> >> On 9/28/17, 8:39 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
> >>
> >> >"packaging branch"?
> >> >
> >> >I do think some coordination (wiki?) is in order, because apparently we
> >> >both spend a good deal of time on the same thing...
> >> >
> >> >EdB
> >> >
> >> >
> >> >
> >> >On Thu, Sep 28, 2017 at 5:25 PM, Alex Harui <aha...@adobe.com.invalid>
> >> >wrote:
> >> >
> >> >> In the build.xml files, both are used.  It is a separate work item to
> >> >> shrink it down to one variable.  And a separate work item to rename
> >> >> everything.
> >> >>
> >> >> Until it is safe to push changes, you can use the packaging branch in
> >> >> royale-asjs and apply the commits I pushed yesterday and see if you
> >>can
> >> >> get things working.  I don't doubt there are things I missed because
> >>of
> >> >> how my computer is set up.
> >> >>
> >> >> Thanks,
> >> >> -Alex
> >> >>
> >> >> On 9/28/17, 7:14 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
> >> >>
> >> >> >My guess is that neither is obsolete as both of them reside in
> >> >> >royale-compiler. Maybe we just need to rename them to
> >>COMPILER_SWF_HOME
> >> >> >and COMPILER_JS_HOME. But my compiler knowledge isn’t great so I’d
> >>wait
> >> >> >for more educated answers.
> >> >> >
> >> >> >From: Erik de Bruin<mailto:erikdebr...@apache.org>
> >> >> >Sent: Thursday, September 28, 2017 4:42 PM
> >> >> >To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> >> >> >Subject: FALCON_HOME and FALCONJX_HOME
> >> >> >
> >> >> >Hi,
> >> >> >
> >> >> >I'm confused (again) ;-)
> >> >> >
> >> >> >There used to be (way back when I knew about this stuff) two
> >>'parts' to
> >> >> >the
> >> >> >compiler. Now there is only one repo...
> >> >> >
> >> >> >The documentation (READme) has info about two env vars - FALCON_HOME
> >> >>and
> >> >> >FALCONJX_HOME - you can set if you install the 'parts' of the
> >>compiler
> >> >>in
> >> >> >non-standard locations. With only one compiler repo in Royale, which
> >> >>one
> >> >> >is
> >> >> >obsolete?
> >> >> >
> >> >> >Thanks,
> >> >> >
> >> >> >EdB
> >> >> >
> >> >>
> >> >>
> >> >
> >> >
> >> >--
> >> >Ix Multimedia Software
> >> >
> >> >Jan Luykenstraat 27
> >> >3521 VB Utrecht
> >> >
> >> >T. 06-51952295
> >> >I.
> >> >https://na01.safelinks.protection.outlook.com/?url=
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl
> >>=02%7C01%7C%7Cd32d90407bec4d18102908d5070844fb%
> 7Cfa7b1b5a7b34438794aed2c1
> >>78decee1%7C0%7C0%7C636422654452206837=
> N9n%2BAF%2Be1EPn5QQ%2Bp5TWqdo
> >>HOjoMyhhizRzgPBXBdsI%3D=0=
> >> >02%7C01%7C%7Cc1b663598b5b42669e0a08d506873f12%
> >> 7Cfa7b1b5a7b34438794aed2c178
> >> >decee1%7C0%7C0%7C636422100308217393=mQQBryNKt%
> >> 2B5D6U2fRwUxz3JZSjle21
> >> >64%2FPmo5QwJ5uQ%3D=0
> >>
> >>
> >
> >
> >--
> >Ix Multimedia Software
> >
> >Jan Luykenstraat 27
> >3521 VB Utrecht
> >
> >T. 06-51952295
> >I.
> >https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl=
> >02%7C01%7C%7Cd32d90407bec4d18102908d5070844fb%
> 7Cfa7b1b5a7b34438794aed2c178
> >decee1%7C0%7C0%7C636422654452206837=N9n%2BAF%2Be1EPn5QQ%
> 2Bp5TWqdoHOj
> >oMyhhizRzgPBXBdsI%3D=0
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Product branding

2017-09-28 Thread Erik de Bruin
For now, it seems convenient to do a few quick tweaks to the existing code
(that uses the flex-sdk repo) to get folks like myself up and running with
a working copy of Royale. Postponing having a way to set up Royale on a
clean system (which mine is) makes it very difficult for new devs to join
the project.

The window is short, we can likely get a few former contributors back now
the dust has settled... I understand that y'all have been working with the
SDK on a daily basis for years and this might not seem a priority, but if
setting up a dev machine is anything but dead simple - or at least very
clear - it will make me less motivated. If I have to guess or ask about
more than a few steps in getting this set up, you've lost me. So to speak.

EdB



On Thu, Sep 28, 2017 at 6:03 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> My PLAYERGLOBAL_HOME does not point inside a flex-sdk repo.  It really
> shouldn't.  We allowed it because some folks wanted to point to an Apache
> Flex IDE configuration, but Apache Flex works fine when developing without
> an IDE by pointing PLAYERGLOBAL_HOME elsewhere.  And that's safer since
> you won't accidentally commit non-Apache bits.
>
> In Royale, I think we need to change the build to not need a flex-sdk repo
> at all and treat Apache Flex as an upstream dependency and work from the
> latest releases.
>
> My 2 cents,
> -Alex
>
> On 9/28/17, 8:45 AM, "Erik de Bruin" <e...@ixsoftware.nl> wrote:
>
> >>
> >> That path to playerglobal should not be in flex-sdk.
> >
> >
> >I was talking about the path in the PLAYERGLOBAL_HOME environment
> >variable.
> >That must point to the Flex SDK directory, but in the current procedure in
> >the READme, that doesn't exist yet. I'm rewriting the READme (and adding
> >helper targets in build.xml) to make the task of  a dev-ready Royale
> >install a bit more streamlined.
> >
> >EdB
> >
> >
> >
> >--
> >Ix Multimedia Software
> >
> >Jan Luykenstraat 27
> >3521 VB Utrecht
> >
> >T. 06-51952295
> >I.
> >https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl=
> >02%7C01%7C%7C698eeb29b0384082767f08d506880e57%
> 7Cfa7b1b5a7b34438794aed2c178
> >decee1%7C0%7C0%7C636422103789712683=7V8hdN06uzMXy2Bgrmgt9wWmL%
> 2Fig%2
> >BMYTwGtsRKXPYbs%3D=0
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: Product branding

2017-09-28 Thread Erik de Bruin
>
> That path to playerglobal should not be in flex-sdk.


I was talking about the path in the PLAYERGLOBAL_HOME environment variable.
That must point to the Flex SDK directory, but in the current procedure in
the READme, that doesn't exist yet. I'm rewriting the READme (and adding
helper targets in build.xml) to make the task of  a dev-ready Royale
install a bit more streamlined.

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Re: FALCON_HOME and FALCONJX_HOME

2017-09-28 Thread Erik de Bruin
"packaging branch"?

I do think some coordination (wiki?) is in order, because apparently we
both spend a good deal of time on the same thing...

EdB



On Thu, Sep 28, 2017 at 5:25 PM, Alex Harui <aha...@adobe.com.invalid>
wrote:

> In the build.xml files, both are used.  It is a separate work item to
> shrink it down to one variable.  And a separate work item to rename
> everything.
>
> Until it is safe to push changes, you can use the packaging branch in
> royale-asjs and apply the commits I pushed yesterday and see if you can
> get things working.  I don't doubt there are things I missed because of
> how my computer is set up.
>
> Thanks,
> -Alex
>
> On 9/28/17, 7:14 AM, "Yishay Weiss" <yishayj...@hotmail.com> wrote:
>
> >My guess is that neither is obsolete as both of them reside in
> >royale-compiler. Maybe we just need to rename them to COMPILER_SWF_HOME
> >and COMPILER_JS_HOME. But my compiler knowledge isn’t great so I’d wait
> >for more educated answers.
> >
> >From: Erik de Bruin<mailto:erikdebr...@apache.org>
> >Sent: Thursday, September 28, 2017 4:42 PM
> >To: dev@royale.apache.org<mailto:dev@royale.apache.org>
> >Subject: FALCON_HOME and FALCONJX_HOME
> >
> >Hi,
> >
> >I'm confused (again) ;-)
> >
> >There used to be (way back when I knew about this stuff) two 'parts' to
> >the
> >compiler. Now there is only one repo...
> >
> >The documentation (READme) has info about two env vars - FALCON_HOME and
> >FALCONJX_HOME - you can set if you install the 'parts' of the compiler in
> >non-standard locations. With only one compiler repo in Royale, which one
> >is
> >obsolete?
> >
> >Thanks,
> >
> >EdB
> >
>
>


-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl


Working on 'build.xml' in 'royale-asjs'

2017-09-28 Thread Erik de Bruin
Hi,

Just to avoid confusion and possible collisions: I'm working on fixing
'build.xml'. I got pulled into it because I'm trying to get back in a dev
mode, but the READme is confusion and inconsistent. This led me to start
fixing it, which then put me squarely in 'build.xml'.

First I'll change the repo URLs, to make sure folks use the Royale ones,
not the old FlexJS ones.

I'm also going to create a few extra (tiny) sub-targets that will allow new
users to use ant to first checkout the required repos. They will then have
to download some additional prerequisites and set some env variables,
before doing a build on all repos to get them into a workable state.

Stay tuned,

EdB