--===============0117632210==
Content-Type: multipart/signed;
  boundary="nextPart25483490.kLtgqhvH1i";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart25483490.kLtgqhvH1i
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

It's not done, and there are problems -- but that doesn't mean that Krita=20
cannot embed a KPresenter document or a KWord document or even a Karbon=20
document -- because it can!

I've just arrived home from a long train journey -- perfect environment for=
=20
coding -- and when the train crossed the bridge over the river IJssel into=
=20
Deventer, I saw a KPresenter document in Krita.

There are some problems, notably the fact that the koffice parts embedding =
is=20
designed for side-by-side embedding, instead of layered embedding, and I'll=
=20
investigate that a bit, but, well -- I'm off to do a little rejoicing first.
=2D-=20
Boudewijn Rempt=20
http://www.valdyas.org/fading/index.cgi

--nextPart25483490.kLtgqhvH1i
Content-Type: application/pgp-signature

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

iD8DBQBCz/gsdaCcgCmN5d8RAovaAJ48eEFk0JXB7S7X8GhHMZKzIhu57gCg8332
VWVuSTCjeDfsWeQixtr2KQs=
=9dLx
-----END PGP SIGNATURE-----

--nextPart25483490.kLtgqhvH1i--

--===============0117632210==
Content-Type: text/plain; charset="iso-8859-1"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel

--===============0117632210==--