About website actual work in progress

Hi, just want to say that I was the past weeks with heavy work load. For the website I think most of the informative pages are done, and in my point of view the pages that needs more work are HOME and FEATURE. But, in the other hand, we need to make a first release to put some valid info in the

Re: Testing npm deployment

Om, One thing I'm confused about: When I read about NPM publishing [1], it sounds like you can publish a folder of stuff (and/or a gzip of that folder) and thus the binaries shouldn't need to be downloaded off of one of our servers. But it looks like the old FlexJS script and now these scripts

Re: Duplicated TextNode in HTML module

In FB, ContainerBase only shows up once in AS code completion and not in MXML (since it isn't in a manifest). HTH, -Alex On 12/16/17, 9:56 AM, "Piotr Zarzycki" wrote: >Anyone who use Flash Builder seeing also duplication ? > >Thanks, Piotr > >2017-12-16 18:47

Re: NPM for Royale (was Re: Repos and Releases)

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

Re: Testing npm deployment

On Sun, Dec 17, 2017 at 10:52 PM, Alex Harui wrote: > Om, > > One thing I'm confused about: When I read about NPM publishing [1], it > sounds like you can publish a folder of stuff (and/or a gzip of that > folder) and thus the binaries shouldn't need to be downloaded

Re: NPM for Royale (was Re: Repos and Releases)

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

Re: NPM for Royale (was Re: Repos and Releases)

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

Re: NPM for Royale (was Re: Repos and Releases)

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

Extraneous Number cast

The following code: var range:XML; // etc. var childLen:int = range.children().length(); compiles to: var /** @type {XML} */ range; // etc. var /** @type {number} */ childLen = Number(range.children().length()); I don’t see why the Number() cast is being added both childLen and

Re: NPM for Royale (was Re: Repos and Releases)

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

Re: NPM for Royale (was Re: Repos and Releases)

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

Testing npm deployment

I have pushed a few changes to my branch: https://github.com/apache/royale-asjs/commits/feature/npm-scripts Can someone give it a look over before I merge it into develop? Once it gets merged into develop, I can test out the build from the lastSuccessfulBuild from the jenkins build. I've given

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

Hi guys, I've replaced Express by Restify at server side and revised the server side implementation a bit. For now, this still is a very simple implementation which is probably enough to start with. I've created a github repo with a short explanation how you can check it out [1]. Of course, I'd

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

On Dec 17, 2017 1:57 PM, "Olaf Krueger" wrote: Hi guys, I've replaced Express by Restify at server side and revised the server side implementation a bit. For now, this still is a very simple implementation which is probably enough to start with. I've created a github repo