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

Martijn Klingens wrote:
>Do you want KDE 3 DCOP to be upwards compatible to KDE 4 IPC or just
> allow KDE 3 apps to work in a KDE 4 environment? The subtle difference
> is that in the latter case we only need to provide the existing
> interfaces without caring about new ones that might appear.
>
>Without talking about possible ways to reach either goals (as I said,
>first collect the issues), I myself would opt for the latter.

And I think we can do better. Without going into the "how", it's difficult=
=20
to decide.

But from the ideas we got last time we discussed D-BUS here, I'd say that=20
it is feasible to give full access to the new environment, not just a=20
compatibility area. In other words, I think the conclusion was:

=2D KDE4 apps will speak D-BUS natively
=2D KDE3 apps can talk to KDE4 apps normally, and vice-versa
=2D KDE3 apps cannot talk to non-KDE D-BUS apps
=2D non-KDE D-BUS apps can send simple messages that are to be relayed into=
=20
DCOP

This would, of course, require that we have a dcopserver. In fact, if we=20
want to support DCOP at all, we'll need dcopserver.

>> Just add the "4" to the name, if the layout of those files is not
>> compatible with the KDE3 apps.
>
>For clarity, the name of the containing folder or the actual filename?

I don't think /etc4 exists, so /etc/kde4rc :-)

In fact, I think we should read both files, as well as both environment=20
variables. The "4" version should override, if found, similarly to what=20
XFree86 did to XF86Config vs XF86Config-4.

> In the latter case e.g. kdeglobals would become kde4globals in $KDEHOME
> as well. (Hmm, might not be a bad idea...)

=2D-=20
  Thiago Macieira  -  thiago (AT) macieira (DOT) info
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

2. T=F3 cennan his weorc gearu, ymbe se circolwyrde, wear=F0 se c=E6gbord a=
nd se=20
leohtspeccabord, and =FEa m=FDs c=F3mon lator. On =FEone d=E6g, he hine res=
te.

--nextPart1666381.2jcjvbh83z
Content-Type: application/pgp-signature

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

iD8DBQBCpYThM/XwBW70U1gRAvO4AJ9wGEA1BhG8FfPhv+YdB5HYpBn8fwCgrgDJ
O1ndAnXPs1mBTnnWU60C1Sk=
=IzSa
-----END PGP SIGNATURE-----

--nextPart1666381.2jcjvbh83z--