k-legacy
k-legacy copied to clipboard
kframework
Develpoing the IntelliJ Idea Plugin for K
Hello. I wanted to develop the IntelliJ Idea plugin for the K language. I want to add features like highlighting of rule LHS/RHS with the rewrite symbol, and folding modules and other things. The current implementation was for Idea 13. My question is should I build on it or just use its code as I progress through the tutorial making a new one from scratch? Has a lot changed from Idea 13 to Idea 2016?
I don't know what changed in IntelliJ, but I would like to help. I always wanted to use the JavaCC parser of the outer K so we have way better control of the syntax declarations. Then we can just think of what efficient stuff we can do for the rules since they are harder to parse.
I tried compiling the current implementation but I couldn't generate the lexer. The instructions say I have to use Idea 12 to do that. But such a small inconvenience made me think of starting from scratch, especially since the tutorial is clear.
@omarz1, it would be great if you could pick this up. We are working on a new API for K and this would be a good opportunity to exercise the API while solving a long-standing problem.
How important is for IntelliJ to use its own parser? Ideally, we would use our own parser and only give IntelliJ the data structures it wants.
OK I decided I will start from scratch and use as much as I can from the current implementation, without sacrificing convenience for future development.
@cos. I still can't estimate the necessity of intelliJ to use its own parser. I have just started using IntelliJ myself and I just got into the language support guide and tutorial. When I reach the stage of the data structures, I will address this point.
@radumereuta, your help will be greatly appreciated. I will keep this thread updated as soon as I reach a compilable version of the plugin.