Re: Ant Build Problem

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'

Re: FAQ page on website

Carlos, Here is my feedback about faq: "Can I have write access to GIT?": It is talking about providing patches by diff etc. I think we should talk there about pull requesting to get used to people to such behavior. "I've used Apache Flex before. How do I start using Apache Royale?" It would

RE: Ant Build Problem

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.

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: Publishing royale to npm

At some point, we could do things like create a pom.xml based on the features they want. For example, the Spring Boot project has this page: https://start.spring.io/ where you could go select the functionalities you want and download the pom.xml. Then you simply run mvn install, and everything

Re: FAQ page on website

Hi Carlos, One question which come up to each of so far created website - Does they need to be checked by someone who is native english speaker ? Thanks, Piotr 2017-11-15 19:52 GMT+01:00 Carlos Rovira : > Hi, > > I put on place a first draft of the FAQ page. You can

FAQ page on website

Hi, I put on place a first draft of the FAQ page. You can review it here: http://royale.codeoscopic.com/faq/ As always, please check it and read to discover : * if the content is what you expect * If sections are ok, and if you want to add more sections. * for the content you consider right if

[Maven|Royale] Maven snapshot artifacts available in the Apache central repository

Hi Guys, About one week ago I have discovered that Maven artifacts for Royale framework are not available in the central Apache repository. Anyone who tried build Hello World with cleaned ".m2" maven folder failed. I just fixed that issue and you can now remove everything from .m2 and build your

Re: Publishing royale to npm

Hi Carlos, IMO, it is a classic trade-off problem. It makes sense that many people want to know exactly what libraries (and versions of those libraries) are being used in the recipe for their app. And, similarly, some people want to know exactly what code is being used in their app and will

Re: Publishing royale to npm

Hi, I must recognize that I'm not fully understand what's the problem. If you use a Royale class to load data, you know it should link Network.swc, To get html controls you use HTML.swc. you want binding? so you refer to Binding.swc. For me this is completely natural. People working with an

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

Re: Publishing royale to npm

Harbs, While technically, it is true that for Royale, the pom.xml files need to have the right SWCs specified, I think if we maintain the archetypes then when you create a new Maven project for an app you will get every SWC specified in your POM, and I don't think there is an issue for having

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

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

RE: Ant Build Problem

I changed ROYALE_SWF_COMPILER_HOME and FLEXUNIT_HOME to match yours but the result is the same. FWIW this is ROYALE_COMPILER_HOME which appears to not resolve correctly: C:\dev\flexjs\royale-asjs\frameworks\projects\Core\src\test\royale>echo %ROYALE_COMPILER_HOME% C:\dev\flexjs\royale-asjs/js

Re: Publishing royale to npm

> why too error-prone? Because it requires users to know which classes are in which swc. I don’t see a reason for that. But, I’m not a Maven user, so take my thoughts with a grain of salt. Harbs > On Nov 15, 2017, at 12:54 PM, Carlos Rovira wrote: > > Hi Harbs, > >

Re: Publishing royale to npm

Hi Harbs, why too error-prone? If you are developing a Royale app with Maven you create a pom, and you add libraries on demand. So your build is totally automated and you only need your project pom in the future and not manually check if libraries are the required ones or not. I see just the

Re: Ant Build Problem

It works for me. It looks like your ROYALE_SWF_COMPILER_HOME is pointing to a different location than mine. Here’s the output I get: CoreTest: check-for-tests: check-compiler-home: check-transpiler-home: check-compiler: test: [available] DEPRECATED - used to override an existing property.

Re: Publishing royale to npm

In case of Maven artifacts the only needs of doing one build is for convenient people who are using Maven build to develop SDK itself. If I'm a user whom would like to use Royale and build my own application by Maven I don't need download repository and build myself whole sources. I just need to

RE: Ant Build Problem

I’m not sure which -config.xml is being used but the ROYALE_COMPILER_HOME is pointing to C:\dev\flexjs\royale-asjs/js The tests are run as part of C:\dev\flexjs\royale-asjs> ant clean all When I try to run the test separately I get

Re: Publishing royale to npm

Hi, I prefer : * only one vote thread * compiler bundled (no release separately) - if people demand it, we always can do that about maven, I remember there's 3 separate builds due to how maven make things, I'd like someone with maven skills could finaly join the three into one, that was

Re: Publishing royale to npm

Hi Piotr, That's fine, we'll see what others think, but we are also discussing whether the compiler is a separate release and vote thread or is bundled with the framework. -Alex On 11/15/17, 12:03 AM, "Piotr Zarzycki" wrote: >Hi, > >Yep we didn't decide it yet how

Re: Publishing royale to npm

Hi, Yep we didn't decide it yet how should be package release. In my opinion this should look like that: 1) Package called royale-flexjs -0.9 Where it compiles to SWF and JS 2) Package called royale-0.9 where it compiles to JS only. I like the idea of voting once where whole framework is in