<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><div>> <span style="font-size:13px;font-family:arial,sans-serif">Glad to see you turned up here.</span><br></div><div><br></div><div>I'm usually lurking around...</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class=""></span>
I agree, but integrating something external with IntelliJ's platform seems like kind of a PITA. It looks like a lot of stuff makes heavy use of PSI trees (see: <a href="https://confluence.jetbrains.com/display/IDEADEV/Developing+Custom+Language+Plugins+for+IntelliJ+IDEA#DevelopingCustomLanguagePluginsforIntelliJIDEA-ImplementingaParserandPSI" target="_blank">https://confluence.jetbrains.<u></u>com/display/IDEADEV/<u></u>Developing+Custom+Language+<u></u>Plugins+for+IntelliJ+IDEA#<u></u>DevelopingCustomLanguagePlugin<u></u>sforIntelliJIDEA-<u></u>ImplementingaParserandPSI</a>)<br>
<br>
I'm no expert in developing IntelliJ plugins either though...<br>
</blockquote></div><br></div><div class="gmail_extra">The totally-not-thought-out idea I had was to have the IntelliJ tree map to the results of libdparse.  So each AST (or PSI) call is just a front for the info provided by libdparse (with caching etc).  Then all the work shifts away from writing a parser to writing the hairy integration bits.</div><div class="gmail_extra"><br></div><div class="gmail_extra"><br></div></div>