Replies: 1 comment 1 reply
-
Hi. Overall, I think you're right. Depending on what kind of plugin you want to write you might be able to do it in IntelliJ and then port the code assuming the debugger API is the same/compatible in CLion. If the CLion API you want to use is very different (and I think this means it'll be the proprietary part of CLion), then I'd avoid it altogether because in my experience it's hard to work with non-public API by guessing what it does or decompiling the code. And it will be even harder to support it in the future. Considering the above, some parts of private API in CLion are probably fine to use, e.g. AST/PSI classes (which you can discover with something like this plugin https://plugins.jetbrains.com/plugin/227-psiviewer, maybe I should embed a similar tool into LivePlugin). Hope this helps 🙂 Regards, |
Beta Was this translation helpful? Give feedback.
-
Hi there,
I have just tried out Live Plugin and it seems to be a great help to start developing plugins. At the moment I am writing code in IntelliJ IDEA, as I have kotlin code completion there. But actually I want to write a plugin for debugging C code. To do this, I need to access the CLion specific APIs, which I cannot access in IDEA. Or do I?
If I switch to CLion, I get even less as the IDEA Kotlin magic is gone and I am left with unhighlighted code and guessing what the API of the CLion stuff might be.
Is there a better way?
Beta Was this translation helpful? Give feedback.
All reactions