We could store the icon graphics as serialized QPictures of "recorded"
QSvgRenderer::render()s.
Of course only if we believe that QtSvg is able to render icons (which is what
I believe, given that the "Iso Icons" do the same:
https://doc.qt.io/qtcreator/qtquick-iso-icon-browser.html )
Alessandr
> On 18 Jun 2021, at 14:06, Nicholas Bennett wrote:
>
> I also would like to see the SVG support fixed, that appears to be address
> the root cause.
>
> -Original Message-
> From: Development On Behalf Of Edward
> Welbourne
> Sent: Friday, 18 June 2021 2:28 PM
> To: Volker Hilsheimer
Hi,
On 18/06/2021 13:28, Edward Welbourne wrote:
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).
I also would like to see the SVG support fixed, that appears to be address the
root cause.
-Original Message-
From: Development On Behalf Of Edward
Welbourne
Sent: Friday, 18 June 2021 2:28 PM
To: Volker Hilsheimer
Cc: development@qt-project.org
Subject: Re: [Development] Version-contr
> -Original Message-
> From: Development On Behalf Of
> Edward Welbourne
> Sent: Friday, 18 June 2021 1:28 PM
> To: Volker Hilsheimer
> Cc: development@qt-project.org
> Subject: Re: [Development] Version-controlling the SVGs of built-in icons
>
> Volker Hilsheimer (18 June 2021 11:19) wr
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 fo
Hi all,
We have released Commercial LTS Qt 5.15.5 today! Please read more information
from the release blog post:
https://www.qt.io/blog/commercial-lts-qt-5.15.5-released
Big thanks for everyone involved!
Best regards
Tarja Sundqvist
Release Manager
> On 2021 Jun 18, at 11:19, Volker Hilsheimer wrote:
>
> Hi,
>
>
> 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.
>
> Which makes me think that we should have those SVGs version controlled
To add to this, for the Design Studio property editor and in some cases beyond
we have moved to using an icon font for all our icons. We have a collection of
python scripts that generate a ttf font from a folder of svg images and then
create a csv of the unicode values and corresponding mapping
For completeness since Alessandro mentioned exporting: for qtquickcontrols2,
I've been using the same Inkscape extension that we document for exporting
9-patch images, since it also works with regular images:
https://doc.qt.io/qt-5/qtquickcontrols2-imagine.html#exporting-9-patch-images
From: De
Very interesting topic, indeed. Thanks.
In order to support High-DPI and themed looks in Qt Creator, we switched from a
decade-old collection of PNGs with unknown origins inconsistent looks to having
everything in an SVG document under source control:
https://github.com/qt-creator/qt-creator/
> -Original Message-
> From: Development On Behalf Of
> Volker Hilsheimer
> Sent: Friday, 18 June 2021 11:20 AM
> To: development@qt-project.org
> Subject: [Development] Version-controlling the SVGs of built-in icons
>
> Hi,
>
>
> The majority of time spent on QTBUG-38776 is chasing dow
Hey hey,
Thanks for bringing this up, I’ve been in that situation myself, for example
looking for diagrams in the documentation.
I generally think that assets that make up a product should live together. That
is, the source code, image assets, docs, examples, tests, etc, for a
module/library.
Hi,
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.
Which makes me think that we should have those SVGs version controlled
somewhere. That “somewhere” can either be the respective module reposito
14 matches
Mail list logo
