Re: help for "quick search"

From: Levente Torok <toroklev(at)gmail(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Márton Ákos <makos999(at)gmail(dot)com>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: help for "quick search"
Date: 2009-03-08 11:31:22
Message-ID: 200903081231.22641.TorokLev@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Sunday 08 March 2009, you wrote:
> On Sun, Mar 8, 2009 at 10:17 AM, Levente Torok <toroklev(at)gmail(dot)com> wrote:
> > On Sunday 08 March 2009, you wrote:
> >>
> >> I don't believe that is possible. You shouldn't be implementing the
> >> search result display in that way anyway in my opinion - what you're
> >> implementing there is a filter, not a search. I would expect results
> >> to be listed in a Window, and a double-click on any row should select
> >> and bring the corresponding node into view on the treeview.
> >>
> >
> > I believe it would require too much user interaction and no benefit compared to
> > manual search.
>
> I'm guessing you never worked on a large database? :-)
>
> > I suggest not even to have a search button but do filter operating
> > on-the-fly. This should be similar to the quick search of new synaptic (in ubuntu).
>
> In that case you need to decide whether your are building a filter or
> a search tool. A search tool is what we have on the todo list - a
> filter is likely to be much harder to implement and not be as useful -
> consider a search on a fairly common string. The search tool will list
> all the results in one place and allow you to jump to a specific one,
> having shown other information such as owner and comment in the
> results list, whilst a filter could still leave results scattered in
> various places in the tree and will require you to select each tree
> node in turn to examine the additional detail you need to determine
> which is the item you're interested in.
>

Ok. Call it as a filter but function as a search :)

Look. The problem is the following.
We have exteremely large number of items in the obj browser tree.
In general, this is very unpleasant to manually search for items in the
tree even if we know the exact name of it. For this reason we usually use
psql console since it has mighty tab completion.
If only such a quick filtering functionality would be integrated in the GUI, it would be extremely helpful.
(not to mention the console integrated in the pgadmin)

I wouldn't like to do any click or key hit, if unneccessary and the synaptic's quick seach such as:
http://www.basicconfig.com/files/imagepicker/j/jinlusuh/Screenshot-Synaptic%20quick%20search%20seamonkey.png
are good examples of this but Compiz config, or KDE's control center are worth considering too.

And this is what the project is aiming at.

Lev

--
Blogger of http://fapuma.blogspot.com

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Giuseppe Sacco 2009-03-08 21:32:10 A few questions about srings to be translated
Previous Message Dave Page 2009-03-08 10:34:08 Re: help for "quick search"