--===============1779124108== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-lcmJZyVM/WiC21Dtf6FR" --=-lcmJZyVM/WiC21Dtf6FR Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable El mi=C3=A9, 09-06-2004 a las 15:45, Jamethiel Knorth escribi=C3=B3: > >From: Manuel Amador > >Date: Wed, 09 Jun 2004 14:28:16 -0500 > > > >El mar, 08-06-2004 a las 03:02, Dik Takken escribi=C3=B3: > > > On Mon, 7 Jun 2004, Jamethiel Knorth wrote: > > > > > > > I'm going to post this to core-devel when 3.3 is released. A=20 > >discussion about > > > > optimizing the search backend really belongs there. Some of the peo= ple=20 > >on > > > > there probably will have some really solid ideas about it. > > > > > > Yes I agree, but not before the desired user experience has been defi= ned > > > by us on this list. > > > >Ridiong on this train of thought, > > > >I don't know about internet searches, but I would like a search tool > >that: > > > >1. is available just like kfind is > >2. is available in the file manager > >3. is available in file/open dialogs > >4. performs rich searches and returns results in less than three seconds > >5. automatically updates when a file is changed to match the search > >criteria > >6. lets me search by > > a) date > > b) keywords > > c) any kind of metadata present in the file > > d) full text >=20 > So, what here wasn't in the proposed changes that started this thread? As= =20 > far as I can tell, it is all there. If it is not, please state what is no= t,=20 > so that I can see about where to work it into the UI. >=20 > 1) The proposal included a standalone program like KFind, and a pane of t= hat=20 > which could be embedded as a kpart. check. > 2) The proposal had one section that could be embedded as a kpart, and a=20 > sidebar which could be used in Konqueror. check. > 3) A huge portion to the proposal was dedicated to search options in file= =20 > selection dialogs. check. May I say that your mockups were great. > 4) The results of the searching are really implementation details, not pa= rt=20 > of the interface design. It is assumed the system will be optimized for=20 > speed. check. > 5) That is completely an implementation issue. If it can be done without = too=20 > much overhead, good. check. > 6) Everything you listed is included in the current KFind, and none was=20 > removed in the proposal. criteria 4 and 5 aren't. >=20 > > > [snip] >=20 > _________________________________________________________________ > Looking to buy a house? Get informed with the Home Buying Guide from MSN=20 > House & Home. http://coldwellbanker.msn.com/ >=20 > _______________________________________________ > kde-usability mailing list > kde-usability@kde.org > https://mail.kde.org/mailman/listinfo/kde-usability --=20 Manuel Amador Jefe de I+D +593 (9) 847-7372 Amauta http://www.amautacorp.com/ GNU Privacy Guard key ID: 0xC1033CAD at keyserver.net --=-lcmJZyVM/WiC21Dtf6FR Content-Type: application/pgp-signature; name=signature.asc Content-Description: Esta parte del mensaje =?ISO-8859-1?Q?est=E1?= firmada digitalmente -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQBAyL4ZWyznNMEDPK0RAtb0AJ4zwd/dKC1bneL2yNDGDkmor4ayzQCfZ9qA hlzGJIZ974pzzmogCbFy6WQ= =YUI5 -----END PGP SIGNATURE----- --=-lcmJZyVM/WiC21Dtf6FR-- --===============1779124108== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ kde-usability mailing list kde-usability@kde.org https://mail.kde.org/mailman/listinfo/kde-usability --===============1779124108==--