>1. An overview of the tools would be great. The README does not have a lot >to start with. Or, are there any other documentation that I am missing?
You don't need to read through all of this, but if you want to get a sense of what it was all about, there are a bunch of tutorials, etc. Most are likely out of date [1]: Basic idea: Combination of a cross-compiler and an SDK using dependency injection and implicit lazy loading of dependencies. You write core AS with a simple DI framework based on the google guice project. The SDK made sure everything was there when it was needed. As you saw, you could then create API definitions (think of the playerglobal.swc) for other dependencies that you were available at runtime, whether they be in the browser itself or in another library that was loaded. >2. I see projects for Ember, JQuery, Node, etc. Does this mean that those >frameworks are already supported in Randori? What would it take to add a new >framework (DOJO, for example)? Yes, versions of those were all supported. It really just takes creating an API definition with the right metadata so that the compiler understands what code to generate. I would need to get all involved to agree (which wouldn't be hard) but all of Randori was under an Apache license so that, if at any point, this project took an interest in what we did, it would be easy to fold it back in. We didn't want to do it within the Apache process itself, but we always hoped it might end up back here. [1] https://github.com/RandoriAS/randori-plugin-intellij/wiki/Lesson-01-Project-Setup
