It occurred to me too that a separate SWC for browser APIs would make sense, since Node should only need a subset of JS types from js.swc. I think it's a good idea.
- Josh On Thu, Jun 9, 2016 at 8:17 AM, Alex Harui <aha...@adobe.com> wrote: > > > On 6/9/16, 4:25 AM, "Harbs" <harbs.li...@gmail.com> wrote: > > >Nice. > > > >This should make things much easier. Good direction! > > Thanks. There are some limitations because the naming scheme is > one-dimensional. For example, I did not create a cordova-config.xml > because you might actually use Jquery as the UI framework in a Cordova app > and/or Google Maps in the same app and then we'd need every combination of > configname (jquery-cordova-googlemaps-config.xml) > > Also, it occurred to me that now that we have named configs, we can > re-think some of how the externs SWCs are configured. For example, the > node-config.xml references js.swc, but I'm now wondering if we should > break out the browser APIs from js.swc into a browser.swc so anyone doing > node work won't be offered Window/Document/MouseEvent in the > code-assistance. Then we can make such changes behind the named-configs > and affect fewer people. > > Thoughts? > -Alex > >
