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 20160809"
(→Debugging) |
|||
| Line 14: | Line 14: | ||
=== Debugging === | === Debugging === | ||
| − | * Ilya is mainly working on frontend debugging. We can have a peek here: https://youtu.be/IcTn0fyaK0s. Soon, target Neon.1, we'll | + | * Ilya is mainly working on frontend debugging. We can have a peek here: https://youtu.be/IcTn0fyaK0s. |
| − | ** for now we assume all the resources are mapped/located in under | + | * Soon, target Neon.1, we'll debug HTML, i.e. within Chrome, probably using any free port, not the default one. [internally it is a WIP (hidden) configuration that connects to Chromium launch configuration ] |
| − | ** Gorkem discussed this with Ilya. This is Java WTP-server related, and when this world receives | + | ** for now we assume all the resources are mapped/located in under web app folder, e.g in [https://github.com/ibuziuk/bsuir-coursework/blob/master/src/main/webapp/WEB-INF/servlet-context.xml#L35 this WEB-INF/servlet-context.xml] |
| + | ** Gorkem discussed this with Ilya. This is Java WTP-server related, and when this world receives a URL, usually it is mapped relatively to the deployment descriptor. Indeed, regular web apps are getting the mappings using that model. | ||
* If we want to access mapped resources, we could use URLs. For more info about this, we could ask Rob Stryker. | * If we want to access mapped resources, we could use URLs. For more info about this, we could ask Rob Stryker. | ||
Revision as of 19:37, 9 August 2016
JSDT/Confcalls/Minutes 20160809
- Attendees: Ilya, Angel, Gorkem, Victor, Patrik
- Links: JSDT Open Bugs: https://goo.gl/nPLxeF
Current Status
Indexxing
- Angel is replacing the old code for the indexing. Now it is working at his best. The AST visitor is visiting the DOM AST that came out of Esprima. Parsing is correct. There is more work to do, as when searching it breaks, likely related to indexing.
- We're just fixing the JSDT indexing, to be correct, using JDT indexing as model. Hopefully, once done, It'll come easier moving to CDT-like indexing, when the current indexer will be complete.
- Gorkem note: we already discussed to use the CDT-related indexer (https://www.infoq.com/presentations/java-jdt-index), but for now it is kind of hard understand how to adapt this to JavaScript.
Debugging
- Ilya is mainly working on frontend debugging. We can have a peek here: https://youtu.be/IcTn0fyaK0s.
- Soon, target Neon.1, we'll debug HTML, i.e. within Chrome, probably using any free port, not the default one. [internally it is a WIP (hidden) configuration that connects to Chromium launch configuration ]
- for now we assume all the resources are mapped/located in under web app folder, e.g in this WEB-INF/servlet-context.xml
- Gorkem discussed this with Ilya. This is Java WTP-server related, and when this world receives a URL, usually it is mapped relatively to the deployment descriptor. Indeed, regular web apps are getting the mappings using that model.
- If we want to access mapped resources, we could use URLs. For more info about this, we could ask Rob Stryker.