Re: [DISCUSS] Discuss Release Apache Royale 0.9.1 RC1

> > 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

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

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

Re: Ant Build Problem

re 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/

Re: Ant Build Problem

] [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>

Re: Ant Build Problem

at 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

Re: Ant Build Problem

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 whil

Re: Access to build servers

ne 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 > > > > > > >

Re: Access to build servers

.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, > > >

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

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 >

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

> > 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>

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

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,

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

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

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

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

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

> 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

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

> > 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

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

> > 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

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

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

Re: globalplayer.swc

> > 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

globalplayer.swc

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

Re: [AS2WASM] Proof of concept code available

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:

Re: Ant Build Problem

e 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> w

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

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

[AS2WASM] Proof of concept code available

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

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

> > 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

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

ds/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> > > Author

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

d 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

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

> > 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

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

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... &

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

s 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-o

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

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 s

mxmlc/asjsc command line arguments

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

Re: Eclipse Run configuration setup

> > 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 >

Re: [Royale-ASJS] flexTasks

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

Re: Eclipse Run configuration setup

, 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

Re: Eclipse Run configuration setup

acheRoyale/ > 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

Re: [Royale-ASJS] flexTasks

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.

Re: [Royale-ASJS] flexTasks

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

Re: [Royale-ASJS] flexTasks

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

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

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

Re: Compiler projects setup and tests

ework > 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 compil

Compiler projects setup and tests

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

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

> 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 456a5584140dd707

Re: Github Pages (was Re: Github wikis)

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

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

> > 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

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

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: >

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

> > 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:

Failed build doing 'ant all' on the packaging branch

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:

Re: FALCON_HOME and FALCONJX_HOME

gt; 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 tod

Re: Product branding

ommit 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...@ixsof

Re: Product branding

> > 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

Re: FALCON_HOME and FALCONJX_HOME

mpiler. 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, 2

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

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