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 functionality... Mostly, there is no actual transpiling yet ;-) But, to be fair, a week is not a lot of time to get that 'detail' done ;-) So, what is there to see? I have created a new, completely separate transpiler client (WASTC), and all the code needed to build, package and distribute it. It has currently one output for whatever you put in: a functional wasm module that exports a simple 'add' function. The client has a publisher that creates a viable project as output, compiling the fake transpiled file into a valid binary file, together with a 'glue' file to allow the .wasm file to load in the companion HTML file. The core of the project is a couple of NPM files. The first one is part of the framework and allows you to not only build the new transpiler client, but also to create a new project skeleton. The second one is added to each project skeleton and allows you to build and preview your project. If you're interested, I have created a wiki page with setup instructions[1]. There are a few nasty dependencies, please be patient and keep in mind that WebAssembly is a very young technology and the tools are few and far between. So: with a bit of patience you can build and "use" as2wasm as if it were fully functional. As long as you don't expect it to handle anything but the project skeleton and that there is not yet real transpilation, just a simple placeholder output to make everything work. If you give it a spin, keep me posted and please don't hesitate to be blunt and give me some (constructive) criticism. Thanks and have fun! EdB 1: https://github.com/apache/royale-asjs/wiki/User-Manual-AS2WASM -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
