Find bar - and getting too many results.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Find bar - and getting too many results.

TimM-3
This was discussed before, and maybe its too late to change - but having
used it a while, I do find that the Ctrl-F find bar shows me too many
results.

I wish typing a Class name (with a capital letter) just showed me the
classes - and none of the methods in those classes (unless they are class
methods with a capital), and that typing a method name - beginning with a
lowercase letter just showed me methods.

Having the class and the methods all together means lots more typing to get
from one class to the next.

Interestingly I notice that in Eclipse (probably IntelliJ too) in their
lookup class dialogs they support just typing capital letters for faster
search. e.g. typing SB would show StringBuffer -this is a neat time saving
hack that I notice that many developers use.

If others are interested in this, I'll post it in the feature requests...

Personally find it very exciting that Dolphin is in league with the big guns
like Eclipse and IntelliJ - and when I show my ruby friends the IDE, they
cry... ;-)


Reply | Threaded
Open this post in threaded view
|

Re: Find bar - and getting too many results.

Chris Uppal-3
TimM wrote:

> Interestingly I notice that in Eclipse (probably IntelliJ too) in their
> lookup class dialogs they support just typing capital letters for faster
> search. e.g. typing SB would show StringBuffer -this is a neat time saving
> hack that I notice that many developers use.

That's a nice idea.  I hadn't noticed it in Eclipse.


> Personally find it very exciting that Dolphin is in league with the big
> guns like Eclipse and IntelliJ [...]

I've been trying to avoid saying this, but can no longer resist the temptation
;-)

You have it the wrong way around.  Dolphin has always been /way/ better than
Eclipse.  /Way/ better.  I can't speak for IntelliJ because I only test ran it
for an hour or two (it would fair to say that it's not as bad as Eclipse).
What /has/ changed in this release is that Dolphin has gained equivalents of
the some of the tinsel[*] that Eclipse uses to diguise the underlying poor
design and impoverished functionality.

([*] the word "tinsel" should not be taken as belittling code-completion, etc,
I'm not suggesting that the stuff doesn't have value.  Merely that that value
only applies to superficial aspects of design and development).

All "IMO", of course...

    -- chris