It’s the entry point to your custom plugin, where you can define new languages, editors for special file types, specific actions that can be triggered, settings screens or tool windows (and many more).Īll of these components and how to integrate them are documented in the links above. You can also define how other plugins can integrate with yours via extensions. This is where you tell IntelliJ what components you have, what integrations, and it will know how to load/display them. The plugin.xml you created in “Step 3” is the connection to the outside world (e.g. There are some UI components specific to IntelliJ but they should be very familiar. You can use standard Java Swing components for a custom user interface. The code you write is effectively Java (or Kotlin). I’ll mention a couple of things that stood out to me, as an Android developer reading these docs. I recommend reading about Plugin Components and User Interface Components from the official documentation. The alternativeIdePath refers to the installation path of the IDE, you’ll have to adjust this based on your OS and IDE version.
0 kommentar(er)
