On Mon, 26 Jan 2009 01:26:57 +0100, Daniel Burrows <[email protected]>
wrote:
On Sun, Jan 25, 2009 at 10:50:54PM +0100, Jiri Palecek <[email protected]>
was heard to say:
On Saturday 24 January 2009 16:48:33 Daniel Burrows wrote:
Moreover, I think it is very user hostile to search in the description
by
default. For example, if the user searches for "aptitude" and gets to
the
package "daptup", (s)he'll be probably very disappointed, because there
is no
easy clue to distinguish this from a failed search. If there was some
sort of
highlighting that would show what actually matched, things would have
been
much better.
Maybe. Other people think it's user hostile to *not* search in the
description by default. Personally, I think the big problem is that
Maybe I have written it badly, I don't think the problem is what is
searched, but what is searched in conjunction with the manner of
presenting the results. Try to inspire yourself in the way Google (or your
favourite search engine) presents answers. They
- rank matches in the title higher than matches in the body
- always show the matching part in bold, so you can easily see what has
been matched
Just as the example I wrote: it might be a failed match, it might be a
misspelled (regular) expression, anything. And the user doesn't know which
is the problem. And a n00b won't know to try "~naptitude" either. These
are just the "tiny disappointments" that make the UI suck, read
http://www.joelonsoftware.com/uibook/chapters/fog0000000057.html
the curses UI presents an unusably large list and the user has to use
searching to navigate it, which sort of works if you search on names
and the user happens to sort of know the name of their package...
Probably I'll have to either make "/" in the curses UI search names
instead of descriptions, or change the UI to match the GTK+ UI more
closely (but I don't think I have time to do that and make it right).
Better not, I don't think the GTK UI is any better (honestly, I think it's
worse).
Regards
Jiri Palecek
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
