Broken Binary Compatibility in 3.1.0

[Aaron J. Seigo]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 11 February 2003 01:05, George Staikos wrote:
> - Renaming modules that are loaded by others (like KControl module names! 
> Yes this happened, and broke 3rd party applications!)

hrm... i wasn't aware that the names of kcontrol modules were guarenteed to 
remain constant, nor was it mentioned in any of the discussions around the 
(many) changes made (by many people) ... is this documented somewhere?

> (without breaking the new names too).  Third party apps that run "kcmshell
> <modulename>" are the ones in question, not what the user sees in the
> KControl GUI.

what is an accepted use of launching kcontrol modules directly via kcmshell 
from third party applications? i can understand programs doing this if the 
control panel belongs to that application, but am curious about these third 
party apps and which panels are relied on by third party apps...

given the rather non-static nature of kcontrol (one panel has already 
disappeared in HEAD since 3.1), would it be better to encourage a more 
dynamic method of launching KDE control panels akin to the startServiceBy 
methods?

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE: The 'K' is for 'kick ass'
http://www.kde.org       http://promo.kde.org/3.1/feature_guide.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE+SWIA1rcusafx20MRAjcKAJ0Zo6eB4KNbUyHrDeqLVZ+Gw7KLaACeOFGK
/+HoiPm79uu6SnZKjHZvu7I=
=VKb/
-----END PGP SIGNATURE-----