10 comments

tap tap. prohibited issue?

Sven Steiniger schrieb:

I asked about this some time ago but no solution was recommended.
Any news?

JIRA: http://www.jetbrains.net/jira/browse/IDEA-4810

0

Sven Steiniger wrote:

tap tap. prohibited issue?

Sven Steiniger schrieb:

>> I asked about this some time ago but no solution was recommended.
>> Any news?
>>
>> JIRA: http://www.jetbrains.net/jira/browse/IDEA-4810

It looks like you're going to wait a few weeks or months to see it addressed. I
have several bugs which are of almost infinite priority for me, which are
blocking release of major features of plugins that I'm developing for my team,
which are not being addressed. Unfortunately we plugin developers are not high
priority (which is understandable to me, considering how buggy 5.0 release was).

0

Hello Keith,

>>> I asked about this some time ago but no solution was recommended.
>>> Any news?
>>>
>>> JIRA: http://www.jetbrains.net/jira/browse/IDEA-4810
>>>
KL> It looks like you're going to wait a few weeks or months to see it
KL> addressed. I have several bugs which are of almost infinite priority
KL> for me, which are blocking release of major features of plugins that
KL> I'm developing for my team, which are not being addressed.
KL> Unfortunately we plugin developers are not high priority (which is
KL> understandable to me, considering how buggy 5.0 release was).

In fact, it's not true that plugin developers are not high priority. Bugs
related to our OpenAPI, and in particular Language API, are a high priority
for us, and if you have any bugs in this area which are not getting addressed,
please remind us of their JIRA IDs, and we'll do our best to fix them as
soon as possible.

What is not high priority is new features in the OpenAPI, and problems related
from unintended usage of our internal classes which are not yet part of OpenAPI
(for example, PsiReferenceProvider or XmlLanguage). New features in OpenAPI,
like features in all other areas of the product, are developed as part of
major new feature development, and for various internal reasons (not related
to bugginess of 5.0 release), major new feature development for the next
version of IDEA is starting only now, quite a long time after the release
of 5.0.

The feature discussed in this thread, like many features related to XML language
embedding which Keith has requested, is just that: a new feature in the OpenAPI.
The only solution or answer we can give Sven is: this feature will be part
of OpenAPI in the next major version of IDEA.

--
Dmitry Jemerov
Software Developer
JetBrains, Inc.
http://www.jetbrains.com
"Develop with pleasure!"


0

Dmitry Jemerov (JetBrains) wrote:

Hello Keith,

>>>> I asked about this some time ago but no solution was recommended.
>>>> Any news?
>>>>
>>>> JIRA: http://www.jetbrains.net/jira/browse/IDEA-4810
>>>>

KL> It looks like you're going to wait a few weeks or months to see it
KL> addressed. I have several bugs which are of almost infinite priority
KL> for me, which are blocking release of major features of plugins that
KL> I'm developing for my team, which are not being addressed.
KL> Unfortunately we plugin developers are not high priority (which is
KL> understandable to me, considering how buggy 5.0 release was).

In fact, it's not true that plugin developers are not high priority.
Bugs related to our OpenAPI, and in particular Language API, are a
high priority for us, and if you have any bugs in this area which are
not getting addressed, please remind us of their JIRA IDs, and we'll do
our best to fix them as soon as possible.


The only one which is not a feature request is
http://jetbrains.net/jira/browse/IDEA-5008 which is very frustrating.
SourceGenerating compiler appears to simply not work. I assume because they are
in IDEADEV, these issues are being addressed:
http://jetbrains.net/jira/browse/IDEADEV-2335,
http://jetbrains.net/jira/browse/IDEADEV-2400,
http://jetbrains.net/jira/browse/IDEADEV-2530

Dmitry I hope you don't feel that I was attacking you or your fellow JetBrains
teammates. I understand you are all working to produce great product. I feel
sure that you can relate to my frustration however - my main task at my job is
to develop IDEA plugins, so I have a lot of stake in the plugin API, and I
receive complaints and bug reports for things that I cannot fix until plugin API
is enhanced or fixed.

0

Hi Dmitry,

In fact, it's not true that plugin developers are not high priority.
Bugs related to our OpenAPI, and in particular Language API, are a
high priority for us, and if you have any bugs in this area which are
not getting addressed, please remind us of their JIRA IDs, and we'll do
our best to fix them as soon as possible.


Now that you're asking for it... ;)

http://www.jetbrains.net/jira/browse/IDEA-4174
http://www.jetbrains.net/jira/browse/IDEA-4292
http://www.jetbrains.net/jira/browse/IDEA-5206

http://www.intellij.net/forums/thread.jsp?forum=23&thread=138483

Note that I don't even ask for them to be fixed/implemented, but the issues are still in
IDEA-Feedback which could mean they got lost (how's that possible?). I'd just like to get
some feedback if you (JB) think it's a problem, something worth to consider or not. If
not, no problem, but then please say so, don't keep us in the dark - I generally feel
there are too many requests that keep lingering around in IDEA-Feedback.

What is not high priority is new features in the OpenAPI, and problems
related from unintended usage of our internal classes which are not yet
part of OpenAPI (for example, PsiReferenceProvider or XmlLanguage).


Geez, if for some reason this mess is (partially) my fault for publishing my findings
about non-OpenAPI stuff or encouraging its use, I'm sorry. Really. :-/

The feature discussed in this thread, like many features related to XML
language embedding which Keith has requested, is just that: a new
feature in the OpenAPI. The only solution or answer we can give Sven is:
this feature will be part of OpenAPI in the next major version of IDEA.


Actually, as much as I feel with Sven and the need for this request, I'm totally with you
Dmitry. I wouldn't expect such an API change that would be needed for that and I think
you're right in not doing it in a minor release (if it's a major change and/or might break
other things). Maybe a short sentence clarifying this, posted in the original request,
would have been enough. Again, feedback is the key to happiness, even if it's negative :)
My 2c.

Cheers,
Sascha

0

+What is not high priority is new features in the OpenAPI, and problems related
from unintended usage of our internal classes which are not yet part of OpenAPI
(for example, PsiReferenceProvider or XmlLanguage).+

This is too bad, since a lot of useful plugins could/will be developed. Just think of all those frameworks needing (XML-) configuration files :(

Still I highly appreciate the (inofficial) support given in this forum.

Greetings,
Yann

0

Actually, as much as I feel with Sven and the need for this request, I'm
totally with you Dmitry. I wouldn't expect such an API change that would
be needed for that and I think you're right in not doing it in a minor
release (if it's a major change and/or might break other things). Maybe


The lang-api was out long ago but I simply had no time for writing my
plugin. Now I have the time but some features are missing.
Of course I don't expect heavy changes of the API in an minor release.
But... . It's really crazy. Browsing references works, find usages some
times not.

I don't know when the next major release will be. 3 month, 6 month,
a year? This is quite a long time to wait. So I expected some dirty
work-around, maybe make some non-open-api methods public, but I got
none :(

Sven.

0

Sascha Weinreuter wrote:
>> What is not high priority is new features in the OpenAPI, and problems
>> related from unintended usage of our internal classes which are not
>> yet part of OpenAPI (for example, PsiReferenceProvider or XmlLanguage).


Geez, if for some reason this mess is (partially) my fault for
publishing my findings about non-OpenAPI stuff or encouraging its use,
I'm sorry. Really. :-/


Nah, I think it's more that plugin writers are wanting to do more with
the Custom Language stuff than JB anticipated or had the time to push
into the OpenAPI.

>> The feature discussed in this thread, like many features related to
>> XML language embedding which Keith has requested, is just that: a new
>> feature in the OpenAPI. The only solution or answer we can give Sven
>> is: this feature will be part of OpenAPI in the next major version of
>> IDEA.

I find myself in the unfortunate situation that my custom language
plugins are essentially glorified syntax highlighters because of the
lack of these API features, such as the cross-language reference
providers. Saying that these changes won't make into IDEA until the next
major release means that my plugin is essentially stalled for the next 6
months or however long it takes. It's somewhat disappointing and
embarrassing when one has to explain to co-workers why it won't work and
will not be fixed in the near future.

That's my 2c. Please take it as constructive feedback 8)

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001

0

Sven Steiniger wrote:

I don't know when the next major release will be. 3 month, 6 month,
a year? This is quite a long time to wait. So I expected some dirty
work-around, maybe make some non-open-api methods public, but I got
none :(


Well, the fact that your request was put into IDEADEV might indicate that a solution could
be expected in less than this time (i.e. for the next EAP) if you're lucky.

I just tried something with a JSP file and Expression Language:

${x.foo}

0

I just tried something with a JSP file and Expression Language:

<html>
<%! class Foo {
public int getFoo() { return 1; }
}
%>

<% Foo x = new Foo(); %>
<body>${x.foo}</body>
</html>

Rename, Find Usages and Highlight Usages in File all work, with the limitation that rename
asks to rename "getFoo", which should be acceptable. But basically it works. What problems
do you see?


I have a plugin for an custom language with similar constructs. Eq.
]]>
where "Title" is an reference to static field BLOCK_Title in the related
java-class. Also "name" is an reference to method getName().
So when using Goto Declaration the references fully work. But using
Rename, Fund Usages, ... (from java) they don't, because internally IDEA
processes all files where the related word (BLOCK_Title, getName) was
returned from the WordScanner. So the references with different names
are not found.

0

Please sign in to leave a comment.