> On 18 Jun 2021, at 14:06, Nicholas Bennett <nicholas.benn...@qt.io> wrote: > > I also would like to see the SVG support fixed, that appears to be address > the root cause. > > -----Original Message----- > From: Development <development-boun...@qt-project.org> On Behalf Of Edward > Welbourne > Sent: Friday, 18 June 2021 2:28 PM > To: Volker Hilsheimer <volker.hilshei...@qt.io> > Cc: development@qt-project.org > Subject: Re: [Development] Version-controlling the SVGs of built-in icons > > Volker Hilsheimer (18 June 2021 11:19) wrote: >> The majority of time spent on QTBUG-38776 is chasing down the various >> SVGs from which it’s then trivial to generate PNGs in different >> resolutions. > > The very fact that we're generating PNGs at different resolutions from SVGs, > when decent support for SVG would make that mostly redundant, says we should > be fixing our SVG support (and making it efficient enough to make it > practical to use it). > > Eddy, who illustrates geometry essays with hand-written inline SVGs. > _______________________________________________ > Development mailing list > Development@qt-project.org > https://lists.qt-project.org/listinfo/development
Qt's SVG support lives in QtSvg, which is a separate module, and not even the same repository as qtbase. Some of the topics at Qt Contributors Summit next week are about our repository structure, so that’s perhaps a good time to talk about whether QtSvg should be moved into qtbase, and perhaps merged with QtGui and QtWidgets, respectively. What the performance implications are for rendering SVGs on demand (even when cached into a pixmap) needs to be evaluated as well. Volker _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
