DCOP interface in kicker broke compatibility?

[Brad Hards]

On Thu, 3 Feb 2005 04:46 am, George Staikos wrote:
>    I think the backwards compatibility of DCOP interfaces is more important
> than even binary compatibility of our libraries.  It's not like there are
> many real commercial, binary-only applications out there using kdelibs.  On
> the other hand, there are many scripts and tools using DCOP.  Changing the
> interface breaks those apps.
Scripts shouldn't be counted differently to other applications. If only 
commercial, binary-only applications count to kdelibs, then only commercial, 
obfuscated scripts should too :-).

Perhaps DCOP compatibility should only count when it is formally documented 
though - just as internal ABI need not be maintained. A couple of apps do 
have documented DCOP interfaces (I just wrote such documentation for 
ksnapshot - see posting to kde-doc-english). 

Brad
-------------- 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/20050203/7dd14bcc/attachment.sig>