Future request: intellisense improvements

Here some suggestions for the resharper intellisense that i personally
would like to have in the future.

-> the usage of the wildcard '*' with intelisence just like the Find
Type/File Dialog
1- *partOfType (i gess this might be slow, but nonetheless)

ex-> *Info
Suggests ->DirectoryInfo, FileInfo, ...

2 - Type.*partOfTheMember

ex-> Application.*Exit
Suggests ->Exit(), Exit(CancelEventArgs), AllowExit, ..

-> some key binding while the intellisense is visible to filter further
the available results

ex -> ctrl + m -> only | and methods
ctrl + e -> only | and events
ctrl + p/f -> only | and properties/fields
ctrl + i -> show | hide inherited members
(The key bindings presented are only speculative)

regards, Pedro.

8 comments

Pedro,

This might be dumb question, but when you suggested a key binding for 'Hide inherited members', do we have any way to do that now, and you just want a hotkey for it, or can we not do that now? Meaning that it sounds like a really cool feature, and I can't find it anywhere - the Smart Complete function seems to recognize inherited members, because it highlights the ones that aren't inherited, but filtering them would be way better. It would really cut down on the noise when using a type inherited from something huge like 'Control' or 'Form'. If it is available now, what version is it in and how do I access it, and if it's not, I hope they add this really soon.

Nick

0

Hello Nick,

Regarding if we have a way to hide the Hide inherited members while
using intellisense i guess there isn't no way to do that, there come the
reason for this request to the resharper team and noise reduction is the
objective.

The only way I know to filter down the members of a class is using the
View -> Object Browser of Visual Studio itself and right clicking the
members pane, but you have to leave the code editor and maybe use the
mouse a bit to drill down witch it’s kind of painful.

I guess the filtering down would not be too hard to the resharper team,
but the key bindings could cause some ripple effects on the product that
have to be fixed before releasing such a feature.

Regards,
Pedro

0

Hello,

-> the usage of the wildcard '*' with intelisence just like the Find
Type/File Dialog


That's a thing we considered when code completion were getting some of the
Goto Type features (like abbreviations). Unfortunately, we discovered that
the use of wildcards in completion brings more confusion than advantages.
For instance, consider the a*b expression. We're still looking for a solution
with decent user experience, and it will be implemented as we have one. Performance
is not a problem here.

-> some key binding while the intellisense is visible to filter
further the available results


And this is one more completion list feature planned for some future version
) There're no UX problems here I believe, so it'll be easier to do.


Serge Baltic
JetBrains, Inc — http://www.jetbrains.com
“Develop with pleasure!”


0

Hi,

I just want to give an example of the intellisense which one of yours competitours produce, compare to yours. And this is one of the reasons, many of our devellopers are not willing to make the switch over to resharper.

Is this not something you could add asap?



Attachment(s):
vsexception.JPG
rexception.JPG
0

Hello Hallur,

Do you mean that Visual Studio (or some add-on) suggest not only types starting
with particular sequence, but also types that have that sequence as a start
of any word in the type name? Does it work for any type, or only for Exception
inheritors? If it is not Visual Studio itself, what add-on makes this kind
of Intellisense, so we can investigate it further?

Thanks for suggestion!

Sincerely,
Ilya Ryzhenkov

JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


HJ> Hi,
HJ>
HJ> I just want to give an example of the intellisense which one of
HJ> yours competitours produce, compare to yours. And this is one of the
HJ> reasons, many of our devellopers are not willing to make the switch
HJ> over to resharper.
HJ>
HJ> Is this not something you could add asap?
HJ>


0

Hi Ilya Ryzhenkov,

Thanks for the quick response.

the product is Visual Assist X http://www.wholetomato.com/

This works for all kinds of suggestion. You can se the two other examples i provided.
One other thing which is really a good feature, is that it always remembers the last used suggestion, even after a restart.

Hallur



Attachment(s):
vacalender.JPG
vsDictionary.JPG
0

Hi again,

Is this a difficult thing to implement?

Hallur

0

Regarding "wildcards" for intellisense: Any plans of this in next version?

If "complex" wildcards like "a*b" is source for big confusion, I would think it's suffice to imply (or simply only support) wildcard *a* (however I don't really see why one would get confused).
E.g. when I type A.Foo I want to have a suggestion box listing methods/members starting with "Foo", but after it also those containing "Foo" (like MyFoo, MyFooBar etc.). I find this very valuable when wanting to list the member methods having something to do with "Foo" for instance.

(This, and the "VA View", are the 2 features I miss most when "upgrading" from Visual Assist X).

Thanks.

*Edit: Just noticed it's still "under debate if it's good or bad feature" in a more recent thread http://www.jetbrains.net/devnet/thread/283173 (about the very same 2 features I wrote above) so I guess there's no concrete plan for implementing it (unfortunately).

0

Please sign in to leave a comment.