I see your point, but I would rather have the package name describe the
output format instead of one of the runtimes that can handle that format.
If we output web assembly someday, I would want to use -wasm instead of
listing one or more of the runtimes that can handle that.
My 2 cents,
-Alex
On
On Dec 17, 2017 9:44 PM, "Alex Harui" wrote:
Why "Air" and not "SWF"?
Not sure I understand your logic.
-Alex
SWF is generally associated with Flash Player which is going to go away
soon.
AIR makes it more obvious that we will support AIR runtimes.
Unless of course I am wrong.
Thanks,
Om
Why "Air" and not "SWF"?
Not sure I understand your logic.
-Alex
On 12/17/17, 12:25 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala" wrote:
>I'm making progress on this front.
>
>I will get the apache-royale npm package first. Let's test this out and
>figure out the next steps for the
I thought that naming if npm is the same as binary package. If I was wrong
I'm sorry and let's move on. :)
Piotr
On Sun, Dec 17, 2017, 10:01 OmPrakash Muppirala
wrote:
> On Sun, Dec 17, 2017 at 12:57 AM, Piotr Zarzycki <
> piotrzarzyck...@gmail.com>
> wrote:
>
> > Hi Om,
> >
> > In the other th
On Sun, Dec 17, 2017 at 12:57 AM, Piotr Zarzycki
wrote:
> Hi Om,
>
> In the other thread there is a proposition about package naming. Alex and
> me propose something.
>
> Thanks,
> Piotr
>
I thought that was for naming the binary artifact? This is for naming the
npm package. Did you mean the s
Hi Om,
In the other thread there is a proposition about package naming. Alex and
me propose something.
Thanks,
Piotr
On Sun, Dec 17, 2017, 09:26 OmPrakash Muppirala
wrote:
> I'm making progress on this front.
>
> I will get the apache-royale npm package first. Let's test this out and
> figure
I'm making progress on this front.
I will get the apache-royale npm package first. Let's test this out and
figure out the next steps for the one with swf version.
Would it be better to call it apache-royale-with-air instead of
apache-royale-with-swf?
Thanks,
Om
On Tue, Dec 12, 2017 at 1:34 PM,
b34438794aed2c178decee1%7C0%7C0%
> 7C636488348179522554&
> >sdata=alK66W8KLnCFp9bskeMoSRfTY%2B%2B5Wm0txR7%2FmToEm2c%3D&reserved=0
> >
> >From: Alex Harui<mailto:aha...@adobe.com.INVALID>
> >Sent: Wednesday, December 13, 2017 9:54 PM
> >To: dev@royale
I found this article [1]. Most of our launch scripts are already using
Ant, so Ant might be part of the solution.
Ignoring the answers that hardcode a path, the others use some interesting
techniques that may or may not work for us. For example, one answer uses
Ant's
d64fab
>7c5108d542cd8127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636488372770
>026928&sdata=Ckxw9je0r40nLKraeQx1lRxhS3QIuh7E1elFSYGCmbM%3D&reserved=0
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Thursday, December 14, 2017 10:10 AM
>To: dev@royale.apache.o
gt;sdata=alK66W8KLnCFp9bskeMoSRfTY%2B%2B5Wm0txR7%2FmToEm2c%3D&reserved=0
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Wednesday, December 13, 2017 9:54 PM
>To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>Subject: Re: Repos and Releases
>
19de0c0e6d64fab
>7c5108d542cd8127%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636488372770
>026928&sdata=Ckxw9je0r40nLKraeQx1lRxhS3QIuh7E1elFSYGCmbM%3D&reserved=0
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Thursday, December 14, 2017 10:10 AM
>To: dev@royale.apache.org<mai
r-html-javascript-files
From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Thursday, December 14, 2017 10:10 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Repos and Releases
The asjsc sets configname to "js". It is not configured to compile with
the R
/3892862/eclipse-setting-up-run-configuration-for-html-javascript-files
From: Alex Harui<mailto:aha...@adobe.com.INVALID>
Sent: Thursday, December 14, 2017 10:10 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Repos and Releases
The asjsc sets configname to &quo
Also, I think we can safely add this to the launch configurations to speed them
up:
This disables the IDEs build when launching.
From: Yishay Weiss
Sent: Thursday, December 14, 2017 9:53:17 AM
To: dev@royale.apache.org
Subject: RE: Repos and Releases
?url=https%3A%2F%2Fpaste.a
>>>p
>>>ache.org%2Ffb3I&data=02%7C01%7Caharui%40adobe.com%7C6c1b1a5764ed4b58c02f
>>>0
>>>8d542148301%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636487578222154
>>>4
>>>09&sdata=4nofhHTHjmmfJb93tdcB3wWGZIgOI
o: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Repos and Releases
The JSOnly package doesn't have Language.swc and other SWF support SWFs.
The difference between Language.swc and LanguageJS.swc is that the
Language.swc has definitions compiled with COMPILE::SWF,true.
ection.outlook.com/?url=
>> https%3A%2F%2Fpaste.ap
>> >>ache.org%2Ffb3I&data=02%7C01%7Caharui%40adobe.com%
>> 7C6c1b1a5764ed4b58c02f0
>> >>8d542148301%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C6364875782221544
>> >>09&sdata=4nofhHTHjmm
.com%
> >> 7Cf4463649f2fe48c9b0b708d
> >> >>5
> >> >>4173ee6d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636486888529206710&
> >> >>s
> >> >>data=4nfCQSPt9m3hp%2FqvZOGoPPvOk%2FdrzX0NARCILiOinNc%3D&reserved=
;reserved=0
>>
>>
>>
>>
>>
>>
>> From: Alex Harui
>> Sent: Tuesday, December 12, 2017 10:38:41 PM
>> To: dev@royale.apache.org
>> Subject: Re: Repos and Releases
>>
>> Actually, it was:
>>
> [1] https://paste.apache.org/fb3I
>
>
>
>
>
>
> From: Alex Harui
> Sent: Tuesday, December 12, 2017 10:38:41 PM
> To: dev@royale.apache.org
> Subject: Re: Repos and Releases
>
> Actually, it was:
>
> cd royale-asjs/ide/f
frameworks\projects\Language\target)
>
>
>
> [1] https://paste.apache.org/fb3I
>
>
>
>
>
>
> From: Alex Harui
> Sent: Tuesday, December 12, 2017 10:38:41 PM
> To: dev@royale.apache.org
> Subject: Re: Repos and Releases
>
\frameworks\projects\Language\target)
[1] https://paste.apache.org/fb3I
From: Alex Harui
Sent: Tuesday, December 12, 2017 10:38:41 PM
To: dev@royale.apache.org
Subject: Re: Repos and Releases
Actually, it was:
cd royale-asjs/ide/flashbuilder
ant -f
OK, we can stick with two standalone packages.
FWIW, the CI build finished and I successfully ran:
sudo npm install -g
http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/lastSuccessfulBuil
d/artifact/out/apache-royale-jsonly-0.9.0-bin.tar.gz
The npm progress bar did not show anything at al
ui%40adobe.com%7Cf4463649f2fe48
>>c
>>9b0b708d54173ee6d%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364868885
>>2
>>9206710&sdata=rgtHk9T02d4%2BqFNjRiomfNph0KAZFmPv0bkFdl7P7xw%3D&reserved=0
>>[4]
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpa
On Tue, Dec 12, 2017 at 12:04 PM, Alex Harui
wrote:
> FWIW, we also have the option of making the SWF support more of an
> "add-on" instead of its own package. IOW, right now both packages contain
> mostly the same files and the SWF support is additional files and some
> slightly different setti
FWIW, we also have the option of making the SWF support more of an
"add-on" instead of its own package. IOW, right now both packages contain
mostly the same files and the SWF support is additional files and some
slightly different settings.
An add-on package would just contain the additional file
I think it would be good if we do: apache-royale-x.x.x and
apache-royale-with-swf-x.x.x.
That makes it much clearer.
Thanks,
Om
On Tue, Dec 12, 2017 at 11:04 AM, Alex Harui
wrote:
> OK, I think I got the packaging fixed. The CI server is building it and
> should finish in 90 minutes or so.
>
>
OK, I think I got the packaging fixed. The CI server is building it and
should finish in 90 minutes or so.
You can try it out locally if you want by syncing up and running "ant
release" and pointing NPM at the tar.gz file in the out folder. I think
you need to "npm uninstall flexjs" first. I on
gt; >
>> > > > > On 12/12/17, 12:06 AM, "Yishay Weiss"
>> > wrote:
>> > > > >
>> > > > > >I’m trying to understand what’s going on here, so I’ll ask some
>> > naïve
>> > > > > >questions:
>
ot; as much as it co-packages all 3
> > > repos
> > > > > into one package. IOW, the package has 3 subfolders (royale-asjs,
> > > > > royale-compiler, royale-typedefs).
> > > > >
> > > > > > 2. If so, why does running ant all from royale-asjs c
The package on the CI server aren't working with NPM. I think I messed up
the Ant script. Looking into it now.
-Alex
On 12/12/17, 10:10 AM, "omup...@gmail.com on behalf of OmPrakash
Muppirala" wrote:
>On Dec 12, 2017 8:41 AM, "Alex Harui" wrote:
>
>
>
>On 12/12/17, 3:51 AM, "omup...@gmail.co
On Dec 12, 2017 8:41 AM, "Alex Harui" wrote:
On 12/12/17, 3:51 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>On Dec 12, 2017 12:25 AM, "Alex Harui" wrote:
>
>I just pushed changes to see if it can work. We'll see after the CI
>server builds it. In theory, you will be abl
b34438794aed2c178decee1%7C0%7C0%7C636486888529206710&
>sdata=7zxTC0iyY5U6yDi9qUU0JKm5%2Fi6Q8Tz9v3BHmQ2cuVY%3D&reserved=0
>
>
>
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Tuesday, December 12, 2017 10:15 AM
>To: dev@royale.apache.org<mailto:dev@
quot;merge" as much as it co-packages all
>>3
>> > repos
>> > > > into one package. IOW, the package has 3 subfolders (royale-asjs,
>> > > > royale-compiler, royale-typedefs).
>> > > >
>> > > > > 2. If so, why does running ant al
On 12/12/17, 3:51 AM, "omup...@gmail.com on behalf of OmPrakash Muppirala"
wrote:
>On Dec 12, 2017 12:25 AM, "Alex Harui" wrote:
>
>I just pushed changes to see if it can work. We'll see after the CI
>server builds it. In theory, you will be able to run:
>
>npm install
>https://na01.safe
.INVALID>
Sent: Tuesday, December 12, 2017 10:15 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Repos and Releases
On 12/12/17, 12:06 AM, "Yishay Weiss" wrote:
>I’m trying to understand what’s going on here, so I’ll ask some naïve
>questions:
&g
On Dec 12, 2017 12:25 AM, "Alex Harui" wrote:
I did some reading about NPM this evening. I think that we can use NPM as
a distribution server. It looked like in FlexJS, we still pulled all of
the artifacts from the mirrors, but I don't think that is a requirement.
Now that the current package
d. If you just cloned royale-asjs and run
> > > "ant
> > > > all", the script will still clone the repos, but for me, if I run
> "ant
> > > > all" in the royale-asjs folder of the nightly source package, it
> > doesn't
> > > > clon
compiler and royale-typedefs. Of
> > > course, something might have broken so I will verify that tomorrow.
> > >
> > > > 3. “Folks should have noticed that the
> > > >IDE-compatible folder is now a royale-asjs subfolder in the binary
> > > &g
framework, in other words will re-building the framework from modified
> > >source update this (3) folder?
> >
> > I'm not sure what configuration you are trying, but the source package
> > really is like packaging up the parent folder of the 3 repos and the
> > bi
guration you are trying, but the source package
> really is like packaging up the parent folder of the 3 repos and the
> binary package is really like packaging up the parent folder of the 3
> repos after building everything. So if changes are detected today, they
> should be in this pac
Hi Alex, that seems good to me,
as we have this finished I'll be updating the website with final commands
Thanks
Carlos
2017-12-12 9:25 GMT+01:00 Alex Harui :
> I did some reading about NPM this evening. I think that we can use NPM as
> a distribution server. It looked like in FlexJS, we sti
I did some reading about NPM this evening. I think that we can use NPM as
a distribution server. It looked like in FlexJS, we still pulled all of
the artifacts from the mirrors, but I don't think that is a requirement.
Now that the current package bundles all 3 repos into a tarball, that
artifac
lding everything. So if changes are detected today, they
should be in this package too.
HTH,
-Alex
>
>From: Alex Harui<mailto:aha...@adobe.com.INVALID>
>Sent: Tuesday, December 12, 2017 3:03 AM
>To: dev@royale.apache.org<mailto:dev@royale.apache.org>
>Subject: Re: Rep
<mailto:aha...@adobe.com.INVALID>
Sent: Tuesday, December 12, 2017 3:03 AM
To: dev@royale.apache.org<mailto:dev@royale.apache.org>
Subject: Re: Repos and Releases
I think I have the packaging scripts set up to package the 3 repos into a
single source package. The nightly builds for the p
I think I have the packaging scripts set up to package the 3 repos into a
single source package. The nightly builds for the past few days have been
churning out this new package. Folks should have noticed that the
IDE-compatible folder is now a royale-asjs subfolder in the binary package.
I'll b
Ok I will wait for your final push to develop. In any case it looks good
till now.
Once you update Readme I can make a build - I haven't done ant build for a
while.
Thanks, Piotr
On Wed, Dec 6, 2017, 08:38 Alex Harui wrote:
> Hi Piotr,
>
> I have all 3 feature/rename branches merged into the d
Hi Piotr,
I have all 3 feature/rename branches merged into the develop branch
locally. I'm not sure it is necessary to merge the other way first,
especially in royale-asjs because most of the changes were in the compiler.
I was going to push it tomorrow (for me) so I can babysit the CI servers
i
Hi Alex,
I did merge develop into rename for asjs repo locally, but not sure whether
I can push it to the rename - let me know.
Apart of that you have said that you need volunteers that check whether
there are still places with dependencies to Flash. - What do you mean by
that actually ? Do you me
In that place I think we should have Wiki page called: "How to download IDE
ready Royale framework" - or something similar. It should describe what
kind of package do we have and what people need to do in order to have SWF
output.
I don't think we should have in the title word "binary package" - I
Generally speaking; Required binary artifacts are typically handled as
"System Requirements", and you may have scripting support to set that up if
you like. If the binary is commercial (even if free of charge), there might
be additional redistribution licensing that may prohibit such automated
down
I'm going to try to reply to everyone else in this one post...
Today, for folks just wanting to write an app with Royale, the nightly for
"JSOnly" has everything you need to create JS output, but not SWF output.
The nightly for the "FlexJS" package does not (and can never) bundle the
Adobe playerg
On Dec 2, 2017 11:20 AM, "Piotr Zarzycki" wrote:
As an application developer no. You are getting that package [1] and have
everything what you need to build app to swf an js.
[1]
http://apacheflexbuild.cloudapp.net:8080/job/royale-
asjs/lastSuccessfulBuild/artifact/out/
That's good to know. I
Hi Alex,
Awesome! great work on getting this done.
As others, I think this is huge and should be merged as soon as you can,
once this step is done we can revisit the packaging or see if something
could be refactored or done better to get even more simplicity, but I think
the task as you did is al
As an application developer no. You are getting that package [1] and have
everything what you need to build app to swf an js.
[1]
http://apacheflexbuild.cloudapp.net:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/
Thanks, Piotr
On Sat, Dec 2, 2017, 19:33 OmPrakash Muppirala wrote:
> On
On Dec 2, 2017 9:08 AM, "Piotr Zarzycki" wrote:
Hi Om,
Not sure what do you mean? We have it. You are downloading one zip file and
using it in IDE.
Are we not downloading falcon, gcc etc separately?
Thanks,
Om
Piotr
On Sat, Dec 2, 2017, 17:30 OmPrakash Muppirala wrote:
> With this setu
Hi Om,
Not sure what do you mean? We have it. You are downloading one zip file and
using it in IDE.
Piotr
On Sat, Dec 2, 2017, 17:30 OmPrakash Muppirala wrote:
> With this setup, can we have the binary release package all the
> dependencies in one zip file?
>
> Thanks,
> Om
>
> On Dec 2, 2017
With this setup, can we have the binary release package all the
dependencies in one zip file?
Thanks,
Om
On Dec 2, 2017 8:25 AM, "Harbs" wrote:
> I don’t have much to add. For me, the simpler, the better. The decisions
> should be to get the first release out as quickly as possible and make our
I don’t have much to add. For me, the simpler, the better. The decisions should
be to get the first release out as quickly as possible and make our release
process as easy as it can be so we can release often.
> On Dec 2, 2017, at 2:00 PM, Piotr Zarzycki wrote:
>
> I would also see in the dev
Hi Alex,
Comments inline.
On Fri, Dec 1, 2017, 19:45 Alex Harui wrote:
> Hi,
>
> The CI servers are reporting that the feature/rename branch is building
> and passing tests. Theoretically, this means that there is a way to build
> the compiler, typedefs and framework without any Adobe code (Fl
Hi,
The CI servers are reporting that the feature/rename branch is building
and passing tests. Theoretically, this means that there is a way to build
the compiler, typedefs and framework without any Adobe code (Flash
playerglobal.swc or AIR SDK), and without a Flex SDK. I think we need
some volu
62 matches
Mail list logo
