Develop with Pleasure II: modest missing features

Time for another trip down "Develop with Pleasure" lane, this time to tell us what missing feature would add to your development pleasure.

Let's focus this thread on modest (as in not rewrite the roadmap) features that are missing from IDEA. To give your feature the best chance of implementation and to help JetBrains, please include a JIRA issue with hyperlink. If the topic is one you want to dialog about first to shape the feature request, that's good too as long as you end up with the JIRA issue. Please add a comment about your bug in the post.

Try to keep the focus away from the very recent new feature functionality that is already part of JetBrains' current focus. - this thread is more for older requests, the backlogged, the languishing, the unassigned, the never JIRAed, etc.

FYI - To create an issue, go here & select IDEA feedback:
http://www.jetbrains.net/jira/secure/CreateIssue!default.jspa
Once you add an issue, JetBrains can track it. You might also search the issue tracker to see if your issue has already been added but not implemented.

123 comments
Comment actions Permalink

A popup mentioning F2/Shift-F2 (of course the actual shortcuts rather than these defaults) on the gutter would maybe be helpful.

However I was thinking about mentioning those shortcuts in the option descriptions:
"Go to next error/warning" is quite strange on a radio button menu item,
because when selected it does not go anywhere. When you just read it and you don't
already know that you can traverse inspection results with F2/Shift-F2 you have no clue
at all what the option does. Even when you know about F2/Shift-F2 it takes another
mental hop to connect that with a context menu on a colored square above the gutter.

As far as the text are concerned, you are right: It may confuse beginners.
However at least the "Go to errors first" should be changed because it is just wrong.
"Go to errors only" would be more correct.

Maybe make it a small popup window which has a header above the two options saying
"F2/Shift-F2 behaviour".

Another usability issue: How are you to know that you can right-click on the square?
I don't usually make it a habit and right-click everywhere to see if something happens.
Maybe add "See context menu for options" to the tooltip that appears on mouse over
would help a little here.
Or maybe even better: Show the options on left click and make the square look more
like a button with a raised instead of a sunken border.

0
Comment actions Permalink

I'd like to see some more innovative use of threads. Especially when
opening a project, scanning a filesystem, building indices, etc. If
IDEA could always leave me in some kind of state where I can get some
work done, even while it's doing this scanning/building in the
background, I'd be a lot happer.

0
Comment actions Permalink

I find myself more and more often adding new libraries to modules,
swapping out old libraries for newer version, etc. The process is quite
painful.

The ultimate would be if IDEA could do it for me (automatically
detecting and adding likely jars that I use, and also finding where the
javadoc and source to those libraries are, more or less automatically.)

But I would be happy if I could just cut and paste the full path to
where the library is located, rather than having to dive down all the
way from C:, using a dialog/tree box. This has come up several times
before here and I'm hoping it will get implemented (doesn't seem like a
very hard thing to do...) before the final 7 comes out.

0
Comment actions Permalink

When I'm looking at files in IDEA and I try and pull up a file for which
IDEA doesn't know what the file type means, I have to stop and add it.

I wish IDEA would just assume it's a text file, and let me add the file
type later, in some kind of unobtrusive way.

This would keep from breaking my development flow.

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

PS. Sorry Jon for not posting my issues earlier! I've been extremely busy!

0
Comment actions Permalink

I think adding re-run action to "Messages Compile" window could be
useful - say, if sometimes only separated package is compiled, and there
are some errors in code - it will be convenient to have an ability to
invoke compile/make directly from make output window

Regards,
Andrew

0
Comment actions Permalink

http://www.jetbrains.net/jira/browse/IDEADEV-15235

Andrew Sazonov wrote:

I think adding re-run action to "Messages Compile" window could be
useful - say, if sometimes only separated package is compiled, and there
are some errors in code - it will be convenient to have an ability to
invoke compile/make directly from make output window

Regards,
Andrew



--
Best regards,
Maxim Mossienko
IntelliJ Labs / JetBrains Inc.
http://www.intellij.com
"Develop with pleasure!"

0
Comment actions Permalink

Oops, sorry - didn't notice that there is JIRA issue for this. Anyway,
thank you for quick reply.

http://www.jetbrains.net/jira/browse/IDEADEV-15235

Andrew Sazonov wrote:

>> I think adding re-run action to "Messages Compile" window could be
>> useful - say, if sometimes only separated package is compiled, and
>> there are some errors in code - it will be convenient to have an
>> ability to invoke compile/make directly from make output window
>>
>> Regards,
>> Andrew


0
Comment actions Permalink

Here's one that I think fits the bill :
http://www.jetbrains.net/jira/browse/IDEA-15042

Jon Steelman wrote:

Time for another trip down "Develop with Pleasure" lane, this time to tell us what missing feature would add to your development pleasure.

Let's focus this thread on modest (as in not rewrite the roadmap) features that are missing from IDEA. To give your feature the best chance of implementation and to help JetBrains, please include a JIRA issue with hyperlink. If the topic is one you want to dialog about first to shape the feature request, that's good too as long as you end up with the JIRA issue. Please add a comment about your bug in the post.

Try to keep the focus away from the very recent new feature functionality that is already part of JetBrains' current focus. - this thread is more for older requests, the backlogged, the languishing, the unassigned, the never JIRAed, etc.

FYI - To create an issue, go here & select IDEA feedback:
http://www.jetbrains.net/jira/secure/CreateIssue!default.jspa
Once you add an issue, JetBrains can track it. You might also search the issue tracker to see if your issue has already been added but not implemented.

0
Comment actions Permalink

I was going add this, as well as add/remove jars to classpath for a module via the context menu on the project tree.

0
Comment actions Permalink

When you do an assertEquals in a junit test, and the assertion fails, you get:
Expected :FOO
Actual :BAR

This happens in a fixed-width font, and the word expected is one letter longer than the word actual, so the expected value is one character further to the right than the actual. It would be really helpful if IDEA would put a second space between Actual and the colon. The the two values being compared would line up exactly. I would really appreciate this one.

0
Comment actions Permalink

I was so excited I forgot how to do basic subtraction. The words expected and actual are, of course, two letters different in length.

All the more reason to make the values line up!

0
Comment actions Permalink

JIRA request number please?

--
regards,
--
Alexey Kudravtsev
Software Developer
JetBrains, Inc, http://www.jetbrains.com
"Develop with pleasure!"

"Roman Zabicki" <no_reply@jetbrains.com> wrote in message
news:10744085.1190741029414.JavaMail.itn@is.intellij.net...
>I was so excited I forgot how to do basic subtraction. The words expected
>and actual are, of course, two letters different in length.
>

All the more reason to make the values line up!



0
Comment actions Permalink

I'm going to need a little help there. I followed the link posted by the original poster, and I get the following error message:
Step 1 of 2: Choose the project and issue type...
You have not selected a valid project to create an issue in.
I don't know how or where to select a valid project in which to create an issue. Let me know how, and I'd be happy to create a JIRA request.

0
Comment actions Permalink

Hello Roman,

I'm going to need a little help there. I followed the link posted by
the original poster, and I get the following error message:
Step 1 of 2: Choose the project and issue type...
You have not selected a valid project to create an issue
in.
I don't know how or where to select a valid project in which to create
an issue. Let me know how, and I'd be happy to create a JIRA request.


Select project "IDEA:Feedback".
On next page, select component "Unit Testing. JUnit"

-tt


0
Comment actions Permalink

Where do I select "IDEA:Feedback" ? What URL?

When I go from
http://www.jetbrains.net/jira/secure/BrowseProject.jspa
to
http://www.jetbrains.net/jira/browse/IDEA/component/10195
I don't see a way to create a new feature request.

0
Comment actions Permalink

Hello Roman,

Where do I select "IDEA:Feedback" ? What URL?

When I go from http://www.jetbrains.net/jira/secure/BrowseProject.jspa
to http://www.jetbrains.net/jira/browse/IDEA/component/10195 I don't
see a way to create a new feature request.


There's a link "Create new issue" in the dark-blue on top of every JIRA page.

-tt


0
Comment actions Permalink

Thank you tt. I wasn't logged in on the other screen, so I didn't have the create new request button... D'oh.

The JIRA request number is 15263.

0
Comment actions Permalink

A good tutorial on how to write inspections?? (Okay, not really an IDE feature, I know... but would still be handy. So far I find it quite hard to find any good documentation about it.)

0
Comment actions Permalink

Hello Erik,

A good tutorial on how to write inspections??


I think you can actually create inspections for a structural search pattern.
As for custom inspections, the plugin development package includes an example.
For (much) more examples that you could possibly want, see the IG sources :)

-tt


0
Comment actions Permalink

Hello Erik,

A good tutorial on how to write inspections??


There's the "Comparing References" example-inspection from the Plugin Development Kit and
of course the Inspection Gadgets sources.

Sascha

0
Comment actions Permalink

Hi Sascha (and Taras),

I knew about the example in the PDK, but I'll have a look in the Inspection Gadgets sources!

Btw: where can I find the sources??

Erik

Message was edited by:
Erik Pragt

0
Comment actions Permalink

Hi Erik,

Btw: where can I find the sources??


You can find it in dev-kit ZIP

0
Comment actions Permalink

Create a package and add the following class in it.
Class A{
protected boolean add(Object o){return true;}
}

Find usages for function "add" is done in the WHOLE(?!?) project....
PS: I know that it is a VERY bad function name ... but still it is very
annoying to wait 1-2 minutes to see the search results.


0
Comment actions Permalink

Anti-aliasing has been mentioned before, but I'd love an option to turn on anti-aliasing everywhere - sadly the only place on my desktop that I see aliased fonts is in Idea (where I often end up spending most of my time).

Have people specifically asked for aliased fonts in certain windows in the past? That's the only reason I can imagine for using them, of course I could probably say that about 100 features in Idea that I don't use - and a half dozen or so that I do! ;)

0
Comment actions Permalink

If I do a simple unscientific test on a find usages of a method in my project (about 700k loc), eclipse 3.4 takes 3 seconds, IDEA 7b7348 takes 6 seconds, and Netbeans 60b1 takes 40 seconds(!).

The seconds really start adding up when you try to find usages of all methods in a class or if you do a refactoring, e.g. Generify... which also relies of find usages.

I'm hoping next release they can speed up find usages.

Some Open Jiras related to Find Usages Performance:

Use compiler caches to speed up Find Usages
http://www.jetbrains.net/jira/browse/IDEADEV-12010

Find Usages - Usages of Methods of a Class - Should do one search for each group of overloaded methods in a class
http://www.jetbrains.net/jira/browse/IDEADEV-17409

See here for more discussion:

Find Usages - performance improvement suggestion
http://www.jetbrains.net/jira/browse/IDEADEV-10983

0
Comment actions Permalink

If I do a simple unscientific test on a find usages
of a method in my project (about 700k loc), eclipse
3.4 takes 3 seconds, IDEA 7b7348 takes 6 seconds, and
Netbeans 60b1 takes 40 seconds(!).


Be aware that IDEA searches for uses much more throughly than Eclipse. IDEA searches for a number of "weak" references, like usages in XML files, JSP, string literals and so on. AFAIK, Eclipse will look only for Java code usages.

0
Comment actions Permalink

Hello,

Congratulations for the release of IntelliJ 7,

i filed a new request for a modest feature i'd like to see really soon, in 7.1 that would be great for example :)

http://www.jetbrains.net/jira/browse/IDEA-15893 :Recent List : add a keyboard modifier to show file locations

Gilles

0

Please sign in to leave a comment.