From kde-core-devel Tue Jun 28 18:20:33 2005 From: Thomas Zander Date: Tue, 28 Jun 2005 18:20:33 +0000 To: kde-core-devel Subject: Re: [RFC] One ioslave to rule them all... Message-Id: <20050628182033.GB2362 () planescape ! com> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=111998289216729 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--z6Eq5LdranGa6ru8" --z6Eq5LdranGa6ru8 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 28, 2005 at 07:06:08PM +0200, K??vin Ottens wrote: > Le Mardi 28 Juin 2005 18:45, Thomas Zander a ??crit : > > I'm not sure about that at all; hierarchies are not needed, at least > > having at max 1 level of subdirs is not what I call hierarchical. >=20 > But it is hierarchical... =3D) I'm just stating naming for convenience of discussion. As you want; "The solution to finding data in your homedir is at this moment unclear, what is very clear is that directory structures more then 1 level deep should be avoided for the general public, but not made impossible" =2E.. > But not everything though searching _only_, hence why I still claim that= =20 > you'll need a hierarchy. This conclusion is wrong; just because you (and others) have not fully sol= ved the problem with searching does not mean that the old system of a hierarchy is the only way left to go. There is much more to explore. (document relations, keywords based relati= ons and probably stuff nobody thought of just yet). Again; I'm not going to claim your solution is bad and should be abandoned,= far from it! The basis you seem to hav taken, that a kio-home slave based URL is user visible, and thus hierarchical per definition will IMO limit its (long term) potential. I'd like to be surprised on how user friendly v.s. powerfull you can make the home:// listings... --=20 Thomas Zander --z6Eq5LdranGa6ru8 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.0 (GNU/Linux) iD8DBQFCwZTxCojCW6H2z/QRAm5mAKDpxzLXjrS3hEp31VYxzfy288oyOACfYALB 3svgTNj+rl6CJP08WAUcc1Y= =CvfL -----END PGP SIGNATURE----- --z6Eq5LdranGa6ru8--