Revision as of 12:56, 9 August 2016

JSDT/Confcalls/Minutes 20160607

Attendees: Ilya, Victor, Angel, Gorkem, Patrik Check: JSDT Open Bugs: https://goo.gl/nPLxeF

Current Status

Angel

• updating indexing and fix JSDT that is still uses the old parser code. A lot of this is deprecated, and not well adapted from JDT -> JSDT .
• Go through the code with the new AST Visitor. Already started with this, it seems feasible. Once the change is done, there is a lot of code that can be stripped out.
• The index manager seems ok, despite is quite old. There is a new mechanism we can use, but we'll consider later, when the current mechanism (old parser) is fixed.
• Then, we can adapt the indexing mechanism using the CDT inspired one. (https://www.infoq.com/presentations/java-jdt-index)

Ilya

• Worked on Hotswap Debugging in remote environment
• Working with Shane for having a new mechanism to detect Node on Windows.
• Look a patch about hotswap

Patrik

• Added an Oomph .setup, that is now committed to JSDT. You can use it directly from Oomph installer, see: http://i.imgur.com/FSiQiGA.png
• Install / contribute documentation is updated in this page: https://wiki.eclipse.org/JSDT/Usage

Victor

• Will look also to SourceEditing issues,

Gorkem

• Working on ClosureCompiler. the AST Parser will start using the CC behind the scene.
• Lot of work to understand how CC works and convert into the current Dom AST model.
• Documentation is not great, but it is coming up well. Actually CC provides much more than Esprima. it can even parse TypeScript, generate AST trees for generics, it does support the DOM AST with more details, not loosing AST details as Esprima. CC is also a Linter, so It'll provide a huge amount of error conditions, that we'll discuss how to use. Plus, it is also better error tolerant than Esprima, so it won't stop in many points where Esprima blocked.
• This work in progress is proceeding well, and the main information is available reading the CC code