royale-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Harui <>
Subject Re: Product branding
Date Thu, 28 Sep 2017 18:27:27 GMT
Well, if the window is short, that's a problem.  GitHub is discarding
commits so I'm not sure it makes sense to push a bunch of changes today.
I've just pushed a test commit to see what happens.

I guess I can test building without the flex-sdk repo locally today.


On 9/28/17, 10:08 AM, "Erik de Bruin" <> wrote:

>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.
>On Thu, Sep 28, 2017 at 6:03 PM, Alex Harui <>
>> 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
>> Flex IDE configuration, but Apache Flex works fine when developing
>> 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
>> 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" <> 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
>> >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.
>> >
>> >02%7C01%7C%7C698eeb29b0384082767f08d506880e57%
>> 7Cfa7b1b5a7b34438794aed2c178
>> >decee1%7C0%7C0%7C636422103789712683&sdata=7V8hdN06uzMXy2Bgrmgt9wWmL%
>> 2Fig%2
>> >BMYTwGtsRKXPYbs%3D&reserved=0
>Ix Multimedia Software
>Jan Luykenstraat 27
>3521 VB Utrecht
>T. 06-51952295

View raw message