JSDT/Confcalls/Minutes 20160705

JSDT Weekly Sync 5 July

Attendees: Ilya, Patrik, Angel, Victor, Gorkem

(JSDT Open Bugs: https://goo.gl/nPLxeF)

Status / Updates

Angel: Grunt/Gulp config; working and cleaning content assist. Also workign on reconcile model operations Ilya: Presented JSDT demo in Waldorf, Gerrit change merged for termination of Debug process as separate process w.r.t. main process. Also workign on other issues, including hotswap. Planning to work on Chromium web debugging, as many people want to se Patrik: is writing docs, mainly quickstart attract users . Also will try to fix Oomph setup Victor: is debugging AERI -related bugs, and provinding minor fixes. Oriented to fix issues also related to JBT Shane working on npm support Snjezana working on JSON Schema Stuffs

JSDT

VR: There is a need for NodeJS tools to add special component. Pblm: If we add a package for NodeJS, we should add a component for each feature. Shall we have a fine grained component list ? like Npm, Gulp & Grunt, Debugger, etc. Use Closure Compiler: https://bugs.eclipse.org/bugs/show_bug.cgi?id=497249

Next Release

Neon.1 will be in September Closure compiler will be the evolution for the JSDT Editor. The problem is to map the domtree read from CC, and transform this into JSDT editor AST Nodes. The https://developers.google.com/closure/compiler/ is not exactly using a visitor pattern. Gorkem did some work in past, visible here https://github.com/gorkem/webtools.jsdt/tree/closure_compiler. As we're going to ship ClosureCompiler in Neon.1, is better we save time and avoid fixing Esprima issues. Victor R & Victor S are going to have a talk about type hierarchy, that needs to be fixed. It used to work because JSDT worked a lot like JDT, but this created issues in JS

Still to do

Cleanup of JSDT open reviews https://git.eclipse.org/r/#/q/project:jsdt/webtools.jsdt+status:open