QuickSearch and others

Hello,

1) I'm just wondering, why do you really need such a strange-looking UI to
perform a quick search? Don't you think that a standard edit box will look
better? Certainly this would produce some problems with focusing but at
least there will be no overlapping UI fragments.

2) Don't think the title of File Structure dialog can be of any use. The
full path names are usually so long that you can't see anything.

3) The control layout of File Structure dialog is quite odd. The labels and
the checkbox seem to have no relative vertical alignment at all. The very
same issue exists in most of "generate xxx" dialogs.

Regards.


7 comments
Comment actions Permalink

1) I'm just wondering, why do you really need such a strange-looking UI to
perform a quick search? Don't you think that a standard edit box will look
better? Certainly this would produce some problems with focusing but at
least there will be no overlapping UI fragments.


What's strange with this kind of UI? It seems to be more less standard.
How this alternative UI with edit box could look like?
And what's the probaly with overlapping UI fragments? Does the speedsearch
window overlap anything important?

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"


"Maxim Babenko" <mab@shade.msu.ru> wrote in message
news:canq8q$ier$1@is.intellij.net...

Hello,

>

1) I'm just wondering, why do you really need such a strange-looking UI to
perform a quick search? Don't you think that a standard edit box will look
better? Certainly this would produce some problems with focusing but at
least there will be no overlapping UI fragments.

>

2) Don't think the title of File Structure dialog can be of any use. The
full path names are usually so long that you can't see anything.

>

3) The control layout of File Structure dialog is quite odd. The labels

and

the checkbox seem to have no relative vertical alignment at all. The very
same issue exists in most of "generate xxx" dialogs.

>

Regards.

>
>


0
Comment actions Permalink

2) Don't think the title of File Structure dialog can be of any use. The
full path names are usually so long that you can't see anything.


What do you mean by full path names?

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Maxim Babenko" <mab@shade.msu.ru> wrote in message
news:canq8q$ier$1@is.intellij.net...

Hello,

>

1) I'm just wondering, why do you really need such a strange-looking UI to
perform a quick search? Don't you think that a standard edit box will look
better? Certainly this would produce some problems with focusing but at
least there will be no overlapping UI fragments.

>

2) Don't think the title of File Structure dialog can be of any use. The
full path names are usually so long that you can't see anything.

>

3) The control layout of File Structure dialog is quite odd. The labels

and

the checkbox seem to have no relative vertical alignment at all. The very
same issue exists in most of "generate xxx" dialogs.

>

Regards.

>
>


0
Comment actions Permalink

What do you mean by full path names?

I mean that currently Re#er displays full path name of the file being
edited. But the window caption is usually too narrow to fit it.


0
Comment actions Permalink

OK, that was just my opinion =)

What's strange with this kind of UI? It seems to be more less standard.
How this alternative UI with edit box could look like?

You may have a look at how member navigation is implemented in Visual
Assist.
We still (unfortunately) have some MC++ development in progress, so I use
both of VA and Re#er in my projects
and can make a comparision.

In fact this seems to be a completely different discussion. I agree that
currently Resharper
provides more information about class members (e.g. field and method
argument and return types)
but usually I just need a way to navigate to the desired member -- and to do
this fast.

The only thing I remember about the member is its name. And sometimes it
becomes
difficult to extract the names from the whole bunch of signatures Re#er
displays to me.

So maybe we can have an option to turn off the detailed information about
members
(so having this setting turned off we get only member names without
signatures)?

And what's the probaly with overlapping UI fragments? Does the speedsearch
window overlap anything important?

No, please forget about this, that wasn't something important.
Again, this has nothing in common with functionality -- just visual
impression

Regards.


0
Comment actions Permalink

As I see in build #88 only relative names are displayed in the caption, so
the issue seems to be closed. Thanks!

Regards.


0
Comment actions Permalink

VKJ> How this alternative UI with edit box could look like?
By "standard edit box" I mean edit box used in "Find File" or "Find Class"
windows.

The idea is simple -- these three features are used in the same context --
you invoke them
whenever you want to navigate to some class, file or member. There should be
a strong reason
to provide visually different UI to perform the similar task.


0
Comment actions Permalink

There is some difference though. Go to Class and Go to File features are
context insensitive while File Structure is for the current file.

--
Valentin Kipiatkov
Chief Scientist, Vice President of Product Development
JetBrains, Inc
http://www.jetbrains.com
"Develop with pleasure!"

"Maxim Babenko" <mab@shade.msu.ru> wrote in message
news:cas50a$4fe$1@is.intellij.net...

VKJ> How this alternative UI with edit box could look like?
By "standard edit box" I mean edit box used in "Find File" or "Find Class"
windows.

>

The idea is simple -- these three features are used in the same context --
you invoke them
whenever you want to navigate to some class, file or member. There should

be

a strong reason
to provide visually different UI to perform the similar task.

>
>


0

Please sign in to leave a comment.