Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "JSDT/Confcalls/Minutes 20160419"
| Line 4: | Line 4: | ||
JSDT Quick references: [https://git.eclipse.org/r/#/q/project:jsdt/webtools.jsdt+is:pending JSDT pending changes (excl.SSE)], [https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=14136767&product=JSDT JSDT Open Bugs] | JSDT Quick references: [https://git.eclipse.org/r/#/q/project:jsdt/webtools.jsdt+is:pending JSDT pending changes (excl.SSE)], [https://bugs.eclipse.org/bugs/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&list_id=14136767&product=JSDT JSDT Open Bugs] | ||
| + | |||
| + | == Debugger == | ||
| + | Ilya made an update on Debugger: pending https://git.eclipse.org/r/#/c/70976/, plus did a video on how it works: https://vimeo.com/163414056 | ||
| + | |||
| + | There are limitations in Debugging support, (Hover, Hotspot) Ilya plan to work on this | ||
| + | |||
| + | Nodejs icons are still in RH pipeline, so Ilya added his own: https://issues.jboss.org/browse/DESIGN-812 | ||
| + | |||
| + | CB, VR, GE: We can use it, as Ilya created them from scratch. | ||
| + | |||
| + | Gorkem: the limitations in Hover are well known. --> Ilya will start working on Hotspot first, then on Hover. | ||
| + | |||
| + | Note: Pushing changes to V8 debug sessions it is not linear. Take a look at the video | ||
| + | |||
| + | == UI, Node js Runtime and Launch Config == | ||
| + | Adalberto: Nodejs Runtime is merged, Gorkem is now using it regularly. See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=492017 | ||
| + | |||
| + | Ilya and Adalberto are to work together to create articles for the newsletter. There are still three articles missing: | ||
| + | * ES6, to be added by Gorkem and Victor R. | ||
| + | * Node Launcher and Debugger, to be added by Adalberto and Ilya | ||
| + | * Task Manager, to be added by Ilya | ||
| + | Gorkem, explains how the Node runtime Works currently : | ||
| + | |||
| + | Assume you have a Nodejs runtime on your system, when you try to run with the default runtime it does not work in Mac & Linux. This is because of Incomplete Java path on Bash | ||
| + | |||
| + | Gorkem and Ilya had similar problems before, and they solved that problem in two ways: | ||
| + | # running a full Bash followed by running Node afterwards or | ||
| + | # find where the Nodejs is installed and then sync with that instance. | ||
| + | Orlando will figure out which is the best system, and suggest which one to use. | ||
| + | |||
| + | VR: So, you are starting Bash and Nodejs on the Path.. but What about windows? | ||
| + | |||
| + | GE: Windows does not have this problem, as all the paths are already configured for the application | ||
| + | |||
| + | Note: using the built-in nodejs runtime on Mac and Linux, there is a launch exception caught by code and ignored. So, you will never see | ||
| + | |||
| + | Note: there is a launch exception using the built-in nodejs runtime on Mac and Linux. You will never see this error because the actual core exception is caught somewhere. This needs to be fixed. See "[https://bugs.eclipse.org/bugs/show_bug.cgi?id=491734 Bug 491734] - Launching with Global (System) node.js fails" | ||
| + | |||
| + | == ES6 == | ||
| + | * Gorkem working on ES6 Branch, where the parser is working as best as it could. | ||
| + | |||
| + | * Eugene is providing type binding impl for DOM AST, which is currently going for CQ process. It'll work for binding on the same file, but not for bingings in other files. | ||
| + | |||
| + | * Shane is working on the Outline view to integrate ES6 exports, similarly to the import we'll have a (collapsable) import declaration | ||
| + | |||
| + | * Ian working on Code completion. working on reassigning workflow, see the gollowing Gerrit change | ||
| + | |||
| + | * ( change .. ) | ||
| + | |||
| + | * GE Looking at dependencied for the Closure Compiler, and there is a compile time dependency that is not suitable. However it'll go to Eclipse Orbit after a CQ is completed. | ||
| + | |||
| + | * Esprima is missing a Type for blocks {..} but for ClosureCompiler is not a problem. | ||
| + | |||
| + | * VR: Does it provide some smart error detection (not only syntax). | ||
| + | |||
| + | * GE: Yes, surprisingly, it parses Typescript. i.e. it can warn you if you assign a variable to an object that is not supposed to be of that type (according JS objects). Another advantage is in CCompiler the errors are full objects : better compared to Esprima, where the error is just a String. | ||
| + | |||
| + | * GE: looking also (marginally) into Nodejs JNI Bridge, which has been demoted after EclipseCon | ||
| + | |||
| + | * Bug 492025 - Esprima based parser incorrectly reports invalid regular expression | ||
| + | |||
| + | * h=/(^\/)|(^#)|(^[\w-\d]*:)/ is a valid Regexp, Esprima parser on nodejs is working, but on Nashorn this is recognised as an error. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=492025 | ||
| + | |||
| + | == JSON Editor == | ||
| + | * Victor and Alina merged changes on JSON Editor issues discussed last week: Bug 486860, 490325 and 490378 | ||
| + | |||
| + | * Alina discovered and reported two new bugs and assigned them to herself. As an example: Adding a node that as a sibling of an array, is wrongly intepreted and the node is palced as a child of the Array. | ||
| + | |||
| + | * Note: Angelo would like to implement the missing part of schema definition in JSON Editor. He asked if this change can go into Neon Release. | ||
| + | |||
| + | * This would be nice but, unless this is implemented and tested by early next week, we can not bring it in Neon(.0) .. Maybe with Neon.1 | ||
| + | |||
| + | * Snjezana is working on JSON Formatter. He has an implementation that is working directly on the model. | ||
| + | |||
| + | * Patrik: Has a pending change for @Since. Bug 259958 is merged to PDE, and then we could revert Bug 490143 after Neon Release. | ||
| + | |||
| + | * He had problems in setting up the JSDT dev env, because of updated dependencies. | ||
| + | |||
| + | * GE: the issue shows up if you have not a specific project into your workspace. This prevented someone to contribute, and it is a good reason for having a Target Platform. Use this URL as base for target platform: http://download.eclipse.org/webtools/downloads/drops/R3.8.0/I-latest/repository/ | ||
| + | |||
| + | * Note: MIstria reported an issue with this: we have a site that should be updated after each I-Build, but this is not updated since a long time. | ||
| + | |||
| + | * GE: Follow-up with Releng team and Mickael. | ||
| + | |||
| + | * (see:https://bugs.eclipse.org/bugs/show_bug.cgi?id=490914) | ||
Revision as of 01:59, 26 April 2016
Contents
JSDT/Confcalls/Minutes 20160419
Attendees : Ilya, Alina, Orlando, Chuck, Patrik, Mike R, Adalberto, Ian, Victor, Gorkem,
JSDT Quick references: JSDT pending changes (excl.SSE), JSDT Open Bugs
Debugger
Ilya made an update on Debugger: pending https://git.eclipse.org/r/#/c/70976/, plus did a video on how it works: https://vimeo.com/163414056
There are limitations in Debugging support, (Hover, Hotspot) Ilya plan to work on this
Nodejs icons are still in RH pipeline, so Ilya added his own: https://issues.jboss.org/browse/DESIGN-812
CB, VR, GE: We can use it, as Ilya created them from scratch.
Gorkem: the limitations in Hover are well known. --> Ilya will start working on Hotspot first, then on Hover.
Note: Pushing changes to V8 debug sessions it is not linear. Take a look at the video
UI, Node js Runtime and Launch Config
Adalberto: Nodejs Runtime is merged, Gorkem is now using it regularly. See bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=492017
Ilya and Adalberto are to work together to create articles for the newsletter. There are still three articles missing:
- ES6, to be added by Gorkem and Victor R.
- Node Launcher and Debugger, to be added by Adalberto and Ilya
- Task Manager, to be added by Ilya
Gorkem, explains how the Node runtime Works currently :
Assume you have a Nodejs runtime on your system, when you try to run with the default runtime it does not work in Mac & Linux. This is because of Incomplete Java path on Bash
Gorkem and Ilya had similar problems before, and they solved that problem in two ways:
- running a full Bash followed by running Node afterwards or
- find where the Nodejs is installed and then sync with that instance.
Orlando will figure out which is the best system, and suggest which one to use.
VR: So, you are starting Bash and Nodejs on the Path.. but What about windows?
GE: Windows does not have this problem, as all the paths are already configured for the application
Note: using the built-in nodejs runtime on Mac and Linux, there is a launch exception caught by code and ignored. So, you will never see
Note: there is a launch exception using the built-in nodejs runtime on Mac and Linux. You will never see this error because the actual core exception is caught somewhere. This needs to be fixed. See "Bug 491734 - Launching with Global (System) node.js fails"
ES6
- Gorkem working on ES6 Branch, where the parser is working as best as it could.
- Eugene is providing type binding impl for DOM AST, which is currently going for CQ process. It'll work for binding on the same file, but not for bingings in other files.
- Shane is working on the Outline view to integrate ES6 exports, similarly to the import we'll have a (collapsable) import declaration
- Ian working on Code completion. working on reassigning workflow, see the gollowing Gerrit change
- ( change .. )
- GE Looking at dependencied for the Closure Compiler, and there is a compile time dependency that is not suitable. However it'll go to Eclipse Orbit after a CQ is completed.
- Esprima is missing a Type for blocks {..} but for ClosureCompiler is not a problem.
- VR: Does it provide some smart error detection (not only syntax).
- GE: Yes, surprisingly, it parses Typescript. i.e. it can warn you if you assign a variable to an object that is not supposed to be of that type (according JS objects). Another advantage is in CCompiler the errors are full objects : better compared to Esprima, where the error is just a String.
- GE: looking also (marginally) into Nodejs JNI Bridge, which has been demoted after EclipseCon
- Bug 492025 - Esprima based parser incorrectly reports invalid regular expression
- h=/(^\/)|(^#)|(^[\w-\d]*:)/ is a valid Regexp, Esprima parser on nodejs is working, but on Nashorn this is recognised as an error. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=492025
JSON Editor
- Victor and Alina merged changes on JSON Editor issues discussed last week: Bug 486860, 490325 and 490378
- Alina discovered and reported two new bugs and assigned them to herself. As an example: Adding a node that as a sibling of an array, is wrongly intepreted and the node is palced as a child of the Array.
- Note: Angelo would like to implement the missing part of schema definition in JSON Editor. He asked if this change can go into Neon Release.
- This would be nice but, unless this is implemented and tested by early next week, we can not bring it in Neon(.0) .. Maybe with Neon.1
- Snjezana is working on JSON Formatter. He has an implementation that is working directly on the model.
- Patrik: Has a pending change for @Since. Bug 259958 is merged to PDE, and then we could revert Bug 490143 after Neon Release.
- He had problems in setting up the JSDT dev env, because of updated dependencies.
- GE: the issue shows up if you have not a specific project into your workspace. This prevented someone to contribute, and it is a good reason for having a Target Platform. Use this URL as base for target platform: http://download.eclipse.org/webtools/downloads/drops/R3.8.0/I-latest/repository/
- Note: MIstria reported an issue with this: we have a site that should be updated after each I-Build, but this is not updated since a long time.
- GE: Follow-up with Releng team and Mickael.