[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-usability
Subject:    Re: Designing improved character selector
From:       "Aaron J. Seigo" <aseigo () kde ! org>
Date:       2007-03-04 20:05:11
Message-ID: 200703041305.12017.aseigo () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On March 4, 2007, John Tapsell wrote:
> Fair enough.
>
> What about removing the search button as well?  It could just search
> as type, showing all the results below.

depends on speed; and of course, such search should have a small delay on them 
to allow people to type multiple characters without triggering tons of 
searches before they are done unless you can do proper incremental searches 
in the data set.

i also still think the "hide details" button should go as the splitter can 
move it out of the way; the class implementing this may also want to have a 
method that allows an application to programmatically hide/show the details 
panel (expand/collapse the splitter?)

and if searching through details isn't -that- slow, it could perhaps search 
through them if they are shown and the "Include Details" button could go 
away.

there is either need for a "Search:" label at the top prefacing the search 
line or a setClickMessage("Enter a search term here") called on the 
KLineEdit...

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)

[Attachment #5 (application/pgp-signature)]

_______________________________________________
kde-usability mailing list
kde-usability@kde.org
https://mail.kde.org/mailman/listinfo/kde-usability


[prev in list] [next in list] [prev in thread] [next in thread]