Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "JSDT/Confcalls/Minutes 20160719"

 
Line 16: Line 16:
 
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=419931 Bug 419931] - Array initializer auto-formatting is a hideous, broken nightmare   
 
** [https://bugs.eclipse.org/bugs/show_bug.cgi?id=419931 Bug 419931] - Array initializer auto-formatting is a hideous, broken nightmare   
 
* There is also a question that we should answer:  
 
* There is also a question that we should answer:  
** StackOverflow question: debugging both Java and JavaScript from Eclipse  
+
** StackOverflow question: debugging both Java and JavaScript from Eclipse http://stackoverflow.com/questions/38386091/how-to-debug-javascript-with-eclipse-running-local-tomcat-server
http://stackoverflow.com/questions/38386091/how-to-debug-javascript-with-eclipse-running-local-tomcat-server
+
  
 
* Angel is Working on a prototype for getting rid of the old Compiler, in favor of the new parser. The aim is to have better code completion improving the indexing, and this will boost performances dramatically.
 
* Angel is Working on a prototype for getting rid of the old Compiler, in favor of the new parser. The aim is to have better code completion improving the indexing, and this will boost performances dramatically.

Latest revision as of 05:44, 10 August 2016

JSDT/Confcalls/Minutes 20160719

Status

  • Patrik Completed simple Oomph project setup file: JSDT.setup. he will push the change, blog about using it for JSDT, and make a video.
  • Angel is Working on a prototype for getting rid of the old Compiler, in favor of the new parser. The aim is to have better code completion improving the indexing, and this will boost performances dramatically.
  • Note: After we fixed the indexing, we should consider using a CDT-style indexing, that is said to have great performances.
  • Gorkem Made a release for the Java lang services
  • He started looking into the Closure Compiler (CC). When that will be ready we'll switch the JSDT parser from Esprima to to CC. Then we'll figure out which level of linting and error tolerance we should use.
    • The CC in JSDT, can quickly generate an AST, (without generror) that we can pass to reconcilier and error reporter.

Back to the top