|
|
|
|
| Re: XText to VSCode integration [message #1829905 is a reply to message #1829892] |
Mon, 13 July 2020 16:28   |
 Tomas Öberg
Messages: 14
Registered: February 2020 |
Junior Member |
|
|
Thanks! I know how to do this now. I just need to get past the dependency issue. (It can run the editor via eclipse with the changes in MANIFEST.MF, but the jar running via the vscode extension has problem finding the SymbolKind class I provided in my customized DocumentSymbolKindProvider class).
It started out as a clean maven project but somehow must have gotten this messed up along the way.
[Updated on: Mon, 13 July 2020 16:29] Report message to a moderator |
|
|
| Re: XText to VSCode integration [message #1829910 is a reply to message #1829905] |
Mon, 13 July 2020 18:38 |
|
it should work with pure maven and gradle out of the box.
if you use eclipse/maven tycho you need to adapt the manifest.
in all cases there should be no problem to have the custom DocumentSymbolKindProvider + a dependency to org.eclipse.lsp4j (in the manifest case you need to install/add lsp4j to the target platform.
so what is exactly missing from the jar(s) you are running in vscode?
Twitter : @chrdietrich
Blog : https://www.dietrich-it.de
|
|
|
| Re: XText to VSCode integration [message #1829925 is a reply to message #1829910] |
Tue, 14 July 2020 08:58 |
Tomas Öberg
Messages: 14
Registered: February 2020 |
Junior Member |
|
|
I got it working!
About the old issue: I tried but can't reproduce the old stacktrace. The only issue I had this time around was of the compile version of the classes (where I got complaints about Guice being compiled with version 54 instead of the compatible 52), so I compiled with 1.8 and then it went fine. (I don't mind using java 8 since I'm so used to that anyway.)
This should perhaps be a separate post but I'm not sure I feel this is a problem I need fixed. It's just that I see the default structure is to create the outline with dots for the children nodes instead of actually putting them into their parent node while populating the outline, so I get an outline looking like this:
object
->properties
->properties.object
->properties.object.property
instead of an outline looking this:
object
->properties
->object
->property
But I guess the solution here is the equivalence of what I did before and I this time I need to bind HierarchicalDocumentSymbolService to my own implementation and restructure the hierarchy to my taste (i.e trimming the name prefixes)?
[Updated on: Tue, 14 July 2020 08:59] Report message to a moderator |
|
|
|
|
|
|
|
| Re: XText to VSCode integration [message #1830477 is a reply to message #1829933] |
Mon, 27 July 2020 14:17 |
Tomas Öberg
Messages: 14
Registered: February 2020 |
Junior Member |
|
|
Sorry for not answering this right away. I got occupied with other bugs more important to fix. It seems like the default is HierarchicalDocumentSymbolService.class. It was a bit hard to debug though since I didn't have the sources for the classes in the project. But could at least see file and row so I figured it out.
For anyone else reading this the solution to the above problem of not getting a simple name instead of a qualified in the outline of say vscode, it is fixed easily by adding the SimpleNameProvider to the IDE module, e.g:
public Class<? extends IQualifiedNameProvider> bindIQualifiedNameProvider() {
return SimpleNameProvider.class;
}
I'm not sure why it isn't configured by default but maybe there's a good reason for that.
[Updated on: Mon, 27 July 2020 17:46] Report message to a moderator |
|
|
|
Powered by
FUDForum. Page generated in 0.03907 seconds
] 
Search
Help
Register
Login
Home
