--nextPart16732100.d8Mtk6oSv0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On December 7, 2004 11:44, Frans Englich wrote:
> I would consider that such a low priority it can be neglectable; that
> people need to manually hack files is the bug, not that it's difficult.

seeing as this happens on a regular basis while doing "tech support" on irc=
=20
and via email, it hardly matters what you or i or the purple elephants on m=
y=20
bed think ;-) it happens, it's appreciated and it therefore has value.

simply discounting how people actually use the system as "invalid" is not=20
productive or a way to engender ourselves to users.

a possible answer is "let them use kconfigeditor" but that sounds a lot lik=
e=20
"let them eat cake". unless there are significant wins to changing the form=
at=20
(which i haven't seen yet), i see no reason to toss away human friendly=20
formats.

and no, buzzword compliance or "it's a standard" doesn't cut it. not even=20
close. look at where going with the buzzwordy "standard compliant" CORBA go=
t=20
our sister project, for instance. the Linux desktop is heading towards DBUS=
=20
not because it embodies a tech industry buzzword or is a standard; it's=20
because things like DCOP and DBUS work, plain and simple.

when moving forward with plans for KDE's config system, we should keep thes=
e=20
lessons in mind.

now, for application DATA it's a whole other ballgame. users are=20
expected/expecting to interact with it directly, and so there it could work=
=20
wonders, esp when it comes to interop. c.f. the OASIS format.

=2D-=20
Aaron J. Seigo
Society is Geometric

--nextPart16732100.d8Mtk6oSv0
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBBtf/p1rcusafx20MRAt98AJ4hjplUoNQOBa2McLkzA8p5Kd+QXgCgkZUC
1BP04kBN7gGy48BRyn8tves=
=kcA2
-----END PGP SIGNATURE-----

--nextPart16732100.d8Mtk6oSv0--