[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ide-dev] IntelliJ's OpenAPI / PSI platform.

Hi Bruno,

So far I've never heard of any integration between Eclipse and some IntelliJ APIs. Since the community parts of IJ are in an Eclipse-friendly license, there is no reason to avoid that, so if anyone thinks it's valuable for Eclipse to use JetBrains OSS APIs, I guess it would be totally fine (and better than re-implementing the same thing).

As part of the topics of Platform UI for Oxygen, there's a part about making it easier to integrate new languages in the IDE. The idea is to work on a generic code editor which can understand extensions for the main code editor operations (highlighting, completion...) and enable the right ones according to the file's content-type (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=497871 ). This would allow to make the language engine (responsible of parsing, inference, building, whatever) a blackbox for the editor, and to allow a single editor to pick its features from different engines.
A Go engine based on OpenAPI would be a good candidate to provide such features for Go files as extensions for the generic editor.

About making an implementation of the language server based on OpenAPI, that would be a good idea I guess. However, I have no idea of how difficult that would be. However, the progress on the topic of language servers seem to make it worthy to introduce this indirection.

Note that if you compare to how other tools (Sublime, VSCode...) are doing, consuming some external applications such as gocode, guru... to provide IDE features seems to be a more sustainable idea. Indeed, those CLI applications are often more sustainable that an IDE-specific parser. However, that's specific to the community which is around the target language.

If you get deeper into experiments, please keep us in touch.

Cheers.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets