Compatibility between KDE 3 and KDE 4

[Thiago Macieira]

Maksim Orlovich wrote:
>> So the only possible outcome for this is to have both KDE3 kded and
>> kdeinit and KDE4 kded and kdeinit --- loaded on demand, of course.
>
>klauncher also fits in this to some extent.  An another option, though,
> is to not load the KDE3 kded modules at all, and have the apps use I/O
> slaves, etc., from the 4.0 desktop. Assuming wire compatibility is
> kept. Not sure how to fit kdeinit quite in there, since I promptly
> forgot the details of the kdeinit/klauncher dance.

That's not an option if we want to support third-party kded modules and 
third-party kioslaves.

kdeinit-applications can be fixed by simply exec(2)ing the executable 
instead of loading the module. But that won't work for modules that don't 
have executables, like the kioslaves.

The only way to load a KDE3 kded module or kioslave is to have kded3 and 
klauncher3, as far as I can see it.

As for the protocol problems you mentioned above, it may be time to think 
about any new protocols we write, so that they stay future-compatible. 
Using XML (or any XML binary encoding) is one idea, but not the only one.

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

1. On frumscafte, hwonne time_t wæs náht, se scieppend þone circolwyrde 
wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20050606/00c4eb8f/attachment.sig>