You're correct Alex, rbls were a full SDK OR user library. You could say we developed that global container to make plug and play with IntelliJ instant. Two years, my brain is a bit hazy.
My design decision was, the SWC compiler did a job, we had other compilers that did other jobs. For myself it didn't make sense messing with the SWC compiler. Maybe it was a bad decision who knows, it's history now. Mike On Fri, Apr 17, 2015 at 2:34 AM, Alex Harui <aha...@adobe.com> wrote: > Mike, Fred, > > I spent more time looking at the RBL code from Randori. It could be that > I haven’t fully understood the code, but it appears so far that RBL are a > higher-level container of things, and I’m currently thinking I can do > everything I need in a SWC. > > Do you guys remember what the advantages of RBL are over SWC? AFAICT, RBL > is really a whole SDK: a set of SWCs and related files. I am thinking I > just want to use SWC because Flash Builder understands it. It sounds like > you did a lot of work to make IntelliJ understand RBL. I can’t imagine > trying to get Flash Builder to understand RBL. > > So, I think I only need to add more files (JS files) to the SWC just like > defaults.css and assets can go in a SWC already. And teaching FalconJX to > find its JS files in those SWCs. > > Anyway, let me know your thoughts. I’m packing it in for tonight. > > Thanks, > -Alex > >
