3 ms·
About the open source AVM2, there are in total 3 versions: The tamarin project on Mozilla mercurial with tamarin-central [0] and tamarin-redux [1] Then after
by zwetan 9y ago
About the open source AVM2, there are in total 3 versions:
The tamarin project on Mozilla mercurial with tamarin-central [0] and tamarin-redux [1]
Then after the project got abandoned, Adobe renamed it to avmplus and moved it to github [2] and made a couple updates.
Later on, they moved it to another repo [3], updated it on December 2015 to the equivalent of Flash Player v19.0 and updated it again on Mars 2016 to the equivalent of Flash Player v20.0 (codename rankin).
I maintain a fork/extension named redtamarin [4] which focus mainly on adding native API to make ActionScript 3.0 run on the command-line, shell scripts, server-side, etc.
imho FlasCC/Alchemy/CrossBridge did not take off because it is much harder for dev to produce a project in C++ than in AS3, also why redtamarin took an opposite approach: bring the C API to the AS3 context instead of forcing users to actually write C/C++ code.
[0]: https://hg.mozilla.org/tamarin-central https://hg.mozilla.org/tamarin-central
[1]: https://hg.mozilla.org/tamarin-redux https://hg.mozilla.org/tamarin-redux
[2]: https://github.com/adobe-flash/avmplus https://github.com/adobe-flash/avmplus
[3]: https://github.com/adobe/avmplus https://github.com/adobe/avmplus
[4]: https://github.com/Corsaair/redtamarin https://github.com/Corsaair/redtamarin
- aidos 9y agoInteresting. I wrote a uploader in flash for our photo hosting website many years ago using alchemy. From memory I wrote a wrapper for libjpeg that could do the resizing in C which was then compiled into flash bytecode. That could then be imported into the swf that would handle multiple files drag-drop resize / upload. That all interfaced with the page through some sort of JS bridge. I'm amazed any of it worked to be honest, somehow it managed to chug along for a decade without issue.
- 0x0 9y agoAlchemy also required a per-domain license key to be purchased to unlock various API combinations at runtime. For me this was the biggest shock and definitively a hint that not all was well in flash land. Runtime player licenses were unheard of until then - only the authoring tools cost money. Having to pay up for every swf on every domain certainly put a chilling effect on experimentation around the new APIs.
- zwetan 9y agoAdobe removed the need to have license afterwards
- 0x0 9y agoAs far as I can remember, that reversal came much much later, when flash was already "dead in the water", unfortunately. By that time WebGL and asm.js/WebAssembly was already coming on to the scene. And it really set the stage for questioning adobe's stewardship of the runtime for developers. Fool me once, ...