Thanks. Adobe CEP, is basically CEF[1] with Node.js support rolled in, so you have the full gamut of browser JS APIs along with Node.js ones. To top it off, Adobe added some Adobe app specific stuff to the mix. (i.e. cep, CSInterface, Vulcan,etc.)
Compiling a new SWC which contains all that seems like too much work. I’ll probably just work around the issue by using bracket notation access… (i.e. var cep:cep = window[“cep”];) Please don’t change node.swc. I’d rather have a "node-js.swc" with the subset in addition. Including the subset inside the node swc will not allow it to be used with CEP alongside the full js.swc. [1]https://bitbucket.org/chromiumembedded/cef On Nov 7, 2016, at 11:37 PM, Josh Tynjala <[email protected]> wrote: > As far as I know, there's no way to do it without compiling a new SWC using > the sources from js.swc and including your additional APIs. > > That's not necessarily a bad thing. In fact, I'd say it's a best practice. > Ideally, I would have built node.swc to also include a subset of what's in > js.swc, instead of also including js.swc. Using js.swc for Node.js apps > exposes a bunch of classes that don't actually exist in Node.js. I hope to > clean that up eventually. This Adobe CEP sounds like a similar situation. > It's a different environment, even if there's a lot of overlap. > > - Josh > > On Mon, Nov 7, 2016 at 11:35 AM, Harbs <[email protected]> wrote: > >> Adobe’s CEP has a “cep” object that gets attached to window. It’s used for >> various things including file system access, native processes, etc. >> >> I’d like to use a typedef SWC for typed access to these utilities, but >> window is defined in js.swc (which I also need to use). >> >> Is there a way to attach the cep object to the window object defined in a >> different swc? I expect this issue to come up in other scenarios as well… >> >> Harbs
