--===============1792700206==
Content-Type: multipart/signed;
  boundary="nextPart1440168.PRrC1CQNTM";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

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

On Wednesday 26 April 2006 11:07, Daniel Teske wrote:
> That's for the KBookmarkBar code, KBookmarkMenu is a little bit more
> complicated, as it is using a trick to circumvent binary compatibility
> restrictions. To understand that code, read
> http://developer.kde.org/documentation/other/binarycompatibility.html

Please keep in mind that KDE 4 will not be binary compatible with KDE 3.  I=
t=20
may be nice to try an be binary compatible over DCOP but I don't see that a=
s=20
pressing since we're moving to D-BUS (and does that matter in this case? =20
does the KBookmark stuff use DCOP?)

So feel free to re-architect the code as necessary.  Keep in mind however t=
hat=20
from KDE 4.0 on, new releases will be binary compatible.  So any redesignin=
g=20
that happens should keep in mind binary compatibility issues.  It's easier =
to=20
be binary compatible when you've designed well. ;)

Regards,
 - Michael Pyne

--nextPart1440168.PRrC1CQNTM
Content-Type: application/pgp-signature

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

iD8DBQBET+0cqjQYp5Omm0oRAjzHAKDiVmSqEscPXEbY49P6pskpQJQ7kACg453Q
yQtXM7tfo98jo6ruolmAmLQ=
=seon
-----END PGP SIGNATURE-----

--nextPart1440168.PRrC1CQNTM--

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

 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

--===============1792700206==--