Michael, Thanks for the link. I went through the whole documentation (still have some questions, though). It looks pretty solid. Any reason there has not been much activity on Randori for a while? Are you planning some new updates any time soon?
The cross-compiler is straight up FalconJX, right? Or has there been more modifications done to FalconJX? I would love for parts of Randori getting folded back in. Do you think FlexJS would be a good fit? I do quite a bit of similarities between Randori and FlexJS. At some point I would like to see some nice JQuery (and perhaps Dojo) integration with FlexJS. Any chance the current tools in Randori can be re-purposed and used in FlexJS? Essentially, what I am looking for is a set of AS3 APIs which have an equivalent JavaScript API for the existing JQuery UI library. Any help that can make this happen would be great. Thanks again, for your time. Regards, Om On Mon, Dec 8, 2014 at 11:28 AM, Michael A. Labriola < labri...@digitalprimates.net> wrote: > > >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 > >
