Community
Participate
Working Groups
While investigating using the Orion tools in other IDEs (as plugins) I ran into a lot of pitfalls, mainly around how tightly The tools are tied to Orion services. We should investigate decoupling the core tools from the Orion services so they can be used anywhere (since most of them are based on static analysis of a standard AST). A few places we need to start: 1. do not pass the service registry into any of the commands / implementation classes. 2. separate the implementation of our commands from the Orion API hooks - for example implement the execute() function in javascriptPlugin.js but have the actual work done in the command class 3. Perhaps just have one JavaScript object that imports all of our tools + classes, and then have javaScriptPlugin.js import that and call functions for the desired support.
The refactoring to be done for bug 484136 will also make this much easier.
We will not be turning the plugin into a worker - see the comments on bug 484136. Instead we have a webpack build that creates a consumable bundle out of the tools. The steps, and information about the API are available in the two wiki pages: 1. https://wiki.eclipse.org/Orion/JavaScript/API 2. https://wiki.eclipse.org/Orion/JavaScript/Build
The API has been released, with build steps / instructions / documentation. I think we can call this bug closed. Any incremental changes to the API can be done in their own bugs.
