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

Aaron J. Seigo wrote:
>On Monday 04 August 2008, Ariya Hidayat wrote:
>> > That's what I've been told by trolls at lastest akademy, when
>> > friendly complaining ;-) with them about the quality of
>> > QSvgRenderer. Looks like it's no more the case as WebkitSvg has been
>> > said to be too slow, but I'll let some TT internal that knows stuff
>> > better than me answer.
>>
>> There is no plan (for QSvgRenderer) to support anything else than SVG
>> Tiny.
>
>what would be useful is explaining, plainly and openly, *why* this is
> the case, even if the answer comes down to "we simply don't have enough
> reason to justify investing further in this technology" or "it would be
> too much work to do otherwise".

Answers are:
=2D too complex
=2D not nearly enough demand [*]
=2D would take too much work
=2D main reason: no developer wants to invest his time on it.

[*] we've never been afraid of doing something where only KDE would=20
benefit from or when only KDE demanded it, but look at the other reasons.

Internally, we work much the same way as developers work on KDE: people=20
work on what they want to work on, most of their time. Sure, there are=20
some things that you have to do or parts of the code that you have to=20
maintain but you don't really like (my example: QHttp, QFtp, QLocale),=20
but that's a small fraction of their time.

Since there's no developer feeling passionate about SVG (the last was=20
Zack), the module is in maintenance mode: no new features.

This new developer who I mentioned who started looking into the icon=20
problems that started this thread will try and do something. SVG is not=20
his area (not the same way as it was Zack's) and so he cannot give an=20
answer right now how far he can go. Nor timeframe: this could take as=20
long as Qt 4.6 or 4.7.

The only way for KDE to be sure that this gets done is for someone who=20
likes SVGs and wants to work on QtSvg to send their CV to us and move to=20
Oslo. (Other alternatives that end up in the code getting written but=20
without a work contract can be discussed too)

>but if there is no appetite to extend QSvgRenderer at all (iow, it's in
> pure maintenance mode) then i probably need to know now so i can plan
> how we will work with or around QSvgRenderer in plasma.

Let's discuss in Belgium next week.

=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

--nextPart5594418.Lqh8GzBy5O
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)

iD8DBQBIl/iBM/XwBW70U1gRAisMAKCNlchK2udhOM/3ocBN17wsgMUaAQCglWiK
dNumXYOEYqLlrEvEUb6iSqQ=
=Pa0n
-----END PGP SIGNATURE-----

--nextPart5594418.Lqh8GzBy5O--