From kde-core-devel Wed Aug 06 17:34:25 2008 From: Thiago Macieira Date: Wed, 06 Aug 2008 17:34:25 +0000 To: kde-core-devel Subject: Re: Qt SVG renderer Message-Id: <200808061934.25293.thiago () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=121804410315738 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1826360.nuBQui5vTI" --nextPart1826360.nuBQui5vTI Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Wednesday 06 August 2008 19:03:16 Ariya Hidayat wrote: > Technically we could have a KSvgRenderer that has both QtSvg's and > WebKit's renderers as the back-end (with the same API so that the > applications do not need to be changed). I'm pretty busy with some > other stuff, but I will try to come up with a prototype for this (feel > free to beat me!). Then we can compare both in terms of speed and > performances. Thus, whichever the back-end will be finally chosen, at > least we have solid technical reasons based on this analysis. We already have a KSvgRenderer, which derives from QSvgRenderer and adds=20 support for .svgz. =2D-=20 =A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org =A0 =A0 PGP/GPG: 0x6EF45358; fingerprint: =A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358 --nextPart1826360.nuBQui5vTI Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQBImeChM/XwBW70U1gRAkvbAKCqiDhILFVOHXvvpkw7vhcy+ctMwQCfdNI3 Hel1C8l7n3BuC/fhyZTBnJQ= =BwY4 -----END PGP SIGNATURE----- --nextPart1826360.nuBQui5vTI--