From koffice-devel Tue Aug 29 17:01:20 2006 From: Boudewijn Rempt Date: Tue, 29 Aug 2006 17:01:20 +0000 To: koffice-devel Subject: Eeeeeeeeeeeeek! Now, pay attention... Message-Id: <200608291901.20187.boud () valdyas ! org> X-MARC-Message: https://marc.info/?l=koffice-devel&m=115687303030063 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============0801613066==" --===============0801613066== Content-Type: multipart/signed; boundary="nextPart6047362.MFAG4gAE71"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit --nextPart6047362.MFAG4gAE71 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline When I came back from a meeting this evening I found a fabulously ill-infor= med=20 discussion about Krita and flake and 2.0 in my konversation log. Let me put= =20 you all straight on this subject: * Krita 2.0 will use KOffice flakes and provide flakes. I'm a true flake=20 believer, for all my rows with Thomas about what's what! * The _only_ reason it doesn't already do so is that I was temporarily out = of=20 action. Casper was busy with pigment and after Adrian did the initial porti= ng=20 on his own, I can well believe he needed a bit of a break. And the rest of= =20 the gang was busy with 1.6. * Krita 2.0 will in the first instance have a special layer type to=20 accommodate flakes, just like it now has a parts layer * Krita 2.0 will provide a single layer flake and an image flake shape * I'm not clear on how I will integrate Krita's ui -- that is, the toolbox,= =20 access to filters and so on with the flakes, but I'll probably be able to=20 work something out.=20 * Flake's event system will handle tablet events with the same precision as= =20 Krita's event system does. If it doesn't yet, then it will. * The UI issues of Krita 2.0 are partly due to neglect: if we move to the n= ew=20 toolbox code, we'll have gained a lot. * The painter issues with Krita are as yet an unsolved problem: Adrian=20 designed the current system with Qt4 in mind, but an old version of Qt4, an= d=20 things may have changed. Maybe we'll need to do a redesign of the canvas.=20 Maybe not. I've pinged Adrian about this issue, but haven't heard back from= =20 him. If push comes to shove, I'll start doing this myself. Oh, and as a postscript: I wanted to port Krita to Qt4 because of: * true alpha in QImage (which we use for display, for instance) * Much superior threading support * Improved dock widgets * Improved painting system (yes, really, our current code show that we star= ted in the Qt1.4 days). * Anti-aliased drawing (i.e, smooth circle for the hsv selector) * Chance to move some of our generic code up the stack, making it useful fo= r=20 everyone. * Not just because that would mean we could mooch a decent text object from= =20 KWord 2.0. As another postscript: I think that Krita 1.6 is pretty well finished. Lots of nice new features, = it=20 needs regression testing and stability and then it should be released. And= =20 then the new features can be ported to 2.0 stante pede.=20 =2D-=20 Boudewijn Rempt=20 http://www.valdyas.org/fading/index.cgi --nextPart6047362.MFAG4gAE71 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQBE9HLgdaCcgCmN5d8RAj9aAJ92NuK87+N05txgnCE+QaMbcBdsNwCgvCtR M3q7CLfrhlloED+vynyT8No= =KXW4 -----END PGP SIGNATURE----- --nextPart6047362.MFAG4gAE71-- --===============0801613066== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ koffice-devel mailing list koffice-devel@kde.org https://mail.kde.org/mailman/listinfo/koffice-devel --===============0801613066==--