> On 21 Jun 2021, at 10:38, Edward Welbourne wrote:
>
> 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
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
so-icon-browser.html )
Alessandro
Von: Development im Auftrag von Volker
Hilsheimer
Gesendet: Freitag, 18. Juni 2021 15:28
An: Nicholas Bennett
Cc: development@qt-project.org
Betreff: Re: [Development] Version-controlling the SVGs of built-in icons
> On 18 Jun 2
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) wrote:
>> The majority of time spent on QTBUG-38776 is chasing down the various
>>
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).
-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 PNG
> -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 Hil
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
> 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
ilto:development-boun...@qt-project.org>>
im Auftrag von Volker Hilsheimer
mailto:volker.hilshei...@qt.io>>
Gesendet: Freitag, 18. Juni 2021 11:19
An: development@qt-project.org<mailto:development@qt-project.org>
mailto:development@qt-project.org>>
Betreff: [Development]
From: Development On Behalf Of Alessandro
Portale
Sent: Friday, 18 June 2021 12:00 PM
To: Volker Hilsheimer ; development@qt-project.org
Subject: Re: [Development] Version-controlling the SVGs of built-in icons
Very interesting topic, indeed. Thanks.
In order to support High-DPI and themed looks
a unified approach across the repositories.
Br,
Alessandro
Von: Development im Auftrag von Volker
Hilsheimer
Gesendet: Freitag, 18. Juni 2021 11:19
An: development@qt-project.org
Betreff: [Development] Version-controlling the SVGs of built-in icons
Hi,
The m
> -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 tim
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
15 matches
Mail list logo