From koffice-devel  Wed Oct 26 11:43:47 2005
From: Thomas Zander <zander () kde ! org>
Date: Wed, 26 Oct 2005 11:43:47 +0000
To: koffice-devel
Subject: Re: Making koApplication inherits KUniqueApplication
Message-Id: <200510261343.47735.zander () kde ! org>
X-MARC-Message: https://marc.info/?l=koffice-devel&m=113032708928089
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============1329933802=="

--===============1329933802==
Content-Type: multipart/signed;
  boundary="nextPart4773034.jXh4yaCA8j";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

On Wednesday 26 October 2005 13:03, Clarence Dang wrote:
> > ps. the usability aspect of KConfig changes has been solved many
> > years ago already in the original styleguide.
>
> Have you ever seen the recent file list in KOffice staying in sync
> between windows? =A0It only works if those windows are in the same
> process. =A0So depending on how I invoke KWord (running another instance
> or clicking File / New), I get different behaviour. =A0That is not
> desirable.

Sure, I agree that that does not work as needed, but there is absolutely=20
no need to go and kill a huge gain we have in sharing processes because=20
you have no idea how to fix a little sideeffect.

In the above mentioned styleguide it says that a config is application=20
wide and is effective as soon as OK is clicked. Saying this is impossible=20
is unacceptable to me, its software you can alter so anything is=20
possible.

Directing your question back to kconfig being flaky;
A much easier way to fix this is to mark a config as dirty whenever=20
another process overwrites the config file and reparse/merge when its=20
needed afterwards.

This makes the config class a bit more complex where it needs a concept of=
=20
changed fields (for merging so you know which fields are changed) and=20
needs to do a dnotify or its newest equivalent for finding out about=20
changed files.

Its not hard, and with the current state of the linux kernel we can=20
actually do it, in contrary to when we started KDE3 (when dnotify did not=20
exist yet).

=2D-=20
Thomas Zander

--nextPart4773034.jXh4yaCA8j
Content-Type: application/pgp-signature

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

iD8DBQBDX2vzCojCW6H2z/QRArcdAKDC4zDKtTAwjvrjp51DIid8CZIMogCgvJAo
Bo9QnF0xYpfY0kbTAZlB460=
=CFcK
-----END PGP SIGNATURE-----

--nextPart4773034.jXh4yaCA8j--

--===============1329933802==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

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

--===============1329933802==--