[PSIViewer] Status?

Hi,

What's the status of the PSI plug-in? It doesn't seem to be
updated since more than a year :(.
Is it still actual and usable?

If yes, wouldn't it be better if it were part of the "devkit" plug-in (to
reduce fragmentation and plug-in startup time)?
http://svn.jetbrains.org/idea/Trunk/devkit/

Thanks in advance,

Ahmed.

10 comments
Comment actions Permalink

I use PSIViewer every day, without difficulty. I imagine most of JetBrains does as well.

As for including it in DevKit, it's probably not the best idea to include plugin-development specific stuff on every developer's desktop. If you don't develop plugins, the only thing you have to see of DevKit is when you create a new module, where it's easy to ignore.

--Dave Griffith

0
Comment actions Permalink

As for including it in DevKit, it's probably not the
best idea to include plugin-development specific
stuff on every developer's desktop. If you don't
develop plugins, the only thing you have to see of
DevKit is when you create a new module, where it's
easy to ignore.


I totally agree. And after all there are a lot of plugin developers which aren't interested in PSI at all - me for example I wrote several plugins and didn't install PSIViewer for now... :)

0
Comment actions Permalink

Hello Dave,

DG> I use PSIViewer every day, without difficulty. I imagine most of
DG> JetBrains does as well.

In fact we have an internal tool for viewing PSI structure, but personally
I used PSIViewer a lot when working on Pythonid. It has some minor problems,
but works pretty well in general.

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Comment actions Permalink

Out of pure curiousity, what does the internal tool do differently than PsiViewer?

--Dave Griffith

0
Comment actions Permalink

Internal tool don't know about new Psi. For example.

0
Comment actions Permalink

+1 flag for PsiViewer in DevKit or in Core

0
Comment actions Permalink

-1 for the simple reason that at least in its current state it clutters the UI for about 95% of the regular users and is a bit too unstable because it likes to cause exceptions now and then, especially in Autoscroll to Source mode. I don't think the separate download is a problem, but maybe the PsiViewer should be mentioned on the "official" plugin development page.

Sascha

0
Comment actions Permalink

Exception is no problem for JIRA ;)

0
Comment actions Permalink

What do you mean by "new Psi"? Multiple PSI roots, like JSP files?

Sascha

0
Comment actions Permalink

The your extension of PSI that you will used in plugin. As i know, internal tool support for Language file types, anyway.

0

Please sign in to leave a comment.