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

An option to use the Eclipse compilers -proceedOnError functionality. Useful and a way to shut up the Eclipse weenies;-)
Enabling this would use -proceedOnError so that code with faults still compiles to class files and would also continue any Run/Debug even if the compiler reported errors.

See also:
http://www.intellij.net/forums/thread.jspa?messageID=5003153
http://www.eclipsezone.com/eclipse/forums/t100199.html#92167170

0
Comment actions Permalink

When you think about it's the F4 action that is already incosistent.

In the java editor F4 and Ctrl-B behave exactly the same.
In project tree and other places Ctrl-B does nothing and F4 behaves like Ctrl-B behaves in the editor.

IMHO we would not loose any functionality if the "Jump to Source" and "Go to declaration" actions would be merged into one, and F4, Ctrl-B and middle click would all be shortcuts to that single action.

Am I missing something? Is there any place where F4 and Ctrl-B should actually do different things?

0
Comment actions Permalink

+253

This would IMHO be a true WOW-factor. I could imagine several default grouping strategies for open editors like "group by project", "group by filetype", "group by VCS status", ... as well as an option (OpenAPI / plugin?) to create custom grouping rules.

Regards,
Jens

--
Jens Voß - http://www.jroller.com/jaypeevoss
Everything's all right just code all night
That's because I'm a good old-fashioned Java boy

0
Comment actions Permalink

Feeewww - I'd say the amount you spent on configuring that will more than eat the time advantage you would maybe have by grouping against using the not-so-advanced existing favorites.

Also the time JetBrains would spent in implementing this could well be spent on something else that really helps productivity more.

Even more so on both points if you implement fancy stuff like configurable grouping rules. I'd rather spent time working on my code than endlessly configuring my IDE.

0
Comment actions Permalink

Hi,

I think there are several pretty annoying things:

1) Creation of new class (was discussed before);

2) No ability to customize the way in which new method is created via
intention ("Create method ....")

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

4) VCS - Don't include .iws into default change list (or at least have
option to this)

Oh, and if there will be a way to instruct IDEA to fold logging
stements.... like commons logging

if (fLog.isErrorEnabled())
{
fLog.error("some errorr...");
}

Or if the user will be able to control folding more precisely
(expecially for XML documents based on elements or XPaths....) Just
dreaming....


Regards,
Andrew

0
Comment actions Permalink

Hello Andrew,

4) VCS - Don't include .iws into default change list (or at least have
option to this)


This one is fixed in Selena.

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


0
Comment actions Permalink

Probably this is not a big deal, but there could be small but convenient
feature - add gutter marks for return statemetns as well as for
statements where exceptions are thrown (ones that are not catched in the
method body)....

Sometimes its' reallly annoyting to investigate somebody's code with may
return points for methods and such a tool could improve productivity,
IMHO ...

Just my two cents

Regards,
Andrew

0
Comment actions Permalink

Hello Andrew,

2) No ability to customize the way in which new method is created via
intention ("Create method ....")


What exactly would you like to customize, and why?

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


0
Comment actions Permalink

Probably it could be useful to combine these tools into one - "Override
methods" and "Implement methods". When new class is created, sometimes
it is slightly annoying to use them separately

Regards,
Andrew

0
Comment actions Permalink

Hello Andrew,

Probably this is not a big deal, but there could be small but convenient
feature - add gutter marks for return statemetns as well as for
statements where exceptions are thrown (ones that are not catched in the
method body)....


You can already do something similar by pressing Ctrl-Shift-F7 (Highlight Usages in File) on any
return- or throw-statement. This will highlight all exit points of the method - with a small
exception though: http://www.jetbrains.net/jira/browse/IDEA-13662

Highlighting (or even adding gutter marks for) all methods that can potentially throw an exception
would IMHO be overkill though and could easily result in a mess...

Sascha

0
Comment actions Permalink

Hi Dmitry,

>> 2) No ability to customize the way in which new method is created via
>> intention ("Create method ....")


What exactly would you like to customize, and why?


Well, for example by default the method generated is private. So if
protected or public on is necessary - the user had to change this manually.

For example, if some reusable library is developed, there could be much
more protected methods rather than private ones... I suppose it could be
overkill if inspection will ask for method visibility on every
invocation, but some settings for this could be really convenient, IMHO

0
Comment actions Permalink

Hi Sascha,

>>Probably this is not a big deal, but there could be small but convenient
>>feature - add gutter marks for return statemetns as well as for
>>statements where exceptions are thrown (ones that are not catched in the
>>method body)....


You can already do something similar by pressing Ctrl-Shift-F7 (Highlight Usages in File) on any
return- or throw-statement. This will highlight all exit points of the method - with a small
exception though: http://www.jetbrains.net/jira/browse/IDEA-13662


Yes, you are correct - but I supposed that it could be more visial)

Highlighting (or even adding gutter marks for) all methods that can potentially throw an exception
would IMHO be overkill though and could easily result in a mess...


Yes, you're right... however, I was thinking not about potential places
where exceptions could come from inner methods ((at least, there could
be not declared runtime exception from them), but rather simply about
highlighting "throw" statements...

0
Comment actions Permalink

I know that this issue was discussed before - but answering every time
that I like to open project in new window sometimes makes me crazy....

Can we have on that dialog some check box that will let ther user to say
IDEA sometnig like this - "And never ever ask me again about this.
Never. No way" :)

0
Comment actions Permalink

Note that pressing ctrl-shift-f7 (Highlight Usages in file) on any "return" or "throw" in the method body will highlight all exit points of the method.

0
Comment actions Permalink

I would like (to be able to make) the SHIFT key accellerate mouse wheel scrolling to something like 1/2 or 3/4 of a page up to even a whole page (less a line or two) per increment.

Randall Schulz

0
Comment actions Permalink

Well, I am not sure about rules and such. I could see them being useful, but my vision is something a little more manual, initially.

You create a tab group as you work and give it a name; not sure how much time was lost there. Then I move or open files in that group as needed; granted those will be seconds of time lost forever. :)

But I can see your point. All that time I wasted on setting up Live Templates and Todo; minutes of my life I will never get back. :)

And, favorites does not do it for me; does not even really work into my work flow, at least currently.

There are many things that get implement in IDEA that are of no use to me, for one reason or another, but that doesn't mean I don't think they are useful to others.

0
Comment actions Permalink

javadoc alignment such that:
/**@return This method's return value has to be

  • described in much detail...*/

i.e. "This" and "described" are aligned... Maybe this was only discussed
informally but I think there's already a JIRA issue - which I can't find
at the moment.

regards,

Messi


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
Avatar
Eugene Vigdorchik
Comment actions Permalink

Should be quite easy to implement, PSI is already there. BTW, I rarely need it, but when I do, it really shines:)

0
Comment actions Permalink

It's already there in 7241. Evidently someone there found and fixed it the day before I reported it.

--Dave Griffith

0
Comment actions Permalink

- 'Duplicate statement' which can duplicate a whole method, class, block or statement depending on where the cursor is. Works on the logical level, so if the cursor is over a 'for', it duplicates the whole loop etc.

- Also 'Delete statement' which works similar

- Easy reordering of if/then/else alternatives. I often have something like

if (a) ...
else if (b) ...
else if (c) ...
else ...

and want to reorder it to

if (b) ...
else if (a) ...
else if (c) ...
else ...

or to

if (a) ...
else if (c) ...
else if (b) ...
else ...

Best thing would be to use 'move statement ...' more clever (or use Alt-shift-up/down). It could also allow reordering of

if (x)
else

to

if (!x)
else

0
Comment actions Permalink

+1
I agree

Francesco

0
Comment actions Permalink

Karsten - Can you submit JIRA requests?
Thanks,
Jon

0
Comment actions Permalink

Note that there is already an intention to do this:
+
if (x)
else

to

if (!x)
else
+

Adding a general "Move branch up/down" pair of intentions sounds handy, and not dreadfully difficult. It should probably trigger on either the "if" or the "else".

The duplicating/deleting is currently most easily done by use of Ctrl-W followed by Ctrl-D. I only mention it because of how many people don't know about either of those actions.

--Dave Griffith

0
Comment actions Permalink

Anti-Aliasing please!!

-sergiy

0
Comment actions Permalink

Hello Sergiy,

Anti-Aliasing please!!


If you've got concrete examples, you can add them to http://www.jetbrains.net/jira/browse/IDEA-14554

Sascha

0
Comment actions Permalink

Thanks Sascha.

Hello Sergiy,

>> Anti-Aliasing please!!


If you've got concrete examples, you can add them to http://www.jetbrains.net/jira/browse/IDEA-14554

Sascha

0
Comment actions Permalink

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

Messi schrieb:

javadoc alignment such that:
/**@return This method's return value has to be

  • described in much detail...*/

i.e. "This" and "described" are aligned... Maybe this was only discussed
informally but I think there's already a JIRA issue - which I can't find
at the moment.

regards,

Messi


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

+1 for branch reordering.

and my suggestion:

an "insert subclass"-intention.
lets say i have a few classes which extend or implement an interface z/class z. i now want to add some logic so z, so i convert it to a class (no problem thx to idea, although it tries to make my classes extend 2 other classes if they already extend another one - there should be a warning), call it ZBase and add some protected methods that the subclasses can use, but i still want Z to be the interface defining the api. sure, i could use the extract interface refactoring, but it would be easier if i could tell idea to replace all implement-statements of z by extends zbase and make zbase implement z and leave al usages of z as they are. could be done in a single step.

0
Comment actions Permalink

Add an "All Open Tabs" option to the print dialog

http://www.jetbrains.net/jira/browse/IDEA-14621

0

Please sign in to leave a comment.