qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2 1/3] ui: install logo icons to $prefix/share/icons
Date: Thu, 10 Jan 2019 09:00:27 -0600	[thread overview]
Message-ID: <c471db17-bab0-21e7-d8c2-7f1b8c1ef742@redhat.com> (raw)
In-Reply-To: <20190110120047.25369-2-berrange@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1936 bytes --]

On 1/10/19 6:00 AM, Daniel P. Berrangé wrote:
> QEMU currently installs loogs to $prefix/share/qemu/ which means no GUI

s/loogs/logos/

> toolkit or applications can find them by default.
> 
> The accepted standards for desktop applications declare that application
> logos / icons should be installed under $prefix/share/icons, so use this
> directory location.
> 
> Pre-rendered icons are provided at the standard sizes expected for GUI
> applications, along with the scalable SVG, to ensure maximum portability.
> 
> The PNGs are rendered from the SVG using inkscape, however, this is not
> wired up into the default make rules to avoid requiring inkscape as a
> mandatory tool in build systems / developer workstations..

double trailing '.'. I like that the rules for automating it are there
as a separate make target, and that they are not part of the default
build (and hence the generated files must live in git).  That said,...

> 
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---


> +++ b/ui/icons/Makefile
> @@ -0,0 +1,13 @@
> +
> +# Regenerate bitmaps from the SVG using inkscape CLI export
> +# and ImageMagick. Don't use ImageMagick for the initial
> +# SVG conversion, since it merely calls inkscape, but uses
> +# 96 DPI res resulting in poor quality output.

...should this comment mention that it is intentional that this target
is not part of 'make all'? Should the target be named 'maint-regenerate'
to call attention to the fact that it is a maintainer-specific target?

> +
> +regenerate:
> +	for s in 16 24 32 48 64 128 256 512; \
> +	do \
> +	    inkscape --without-gui --export-png=qemu_$${s}x$${s}.png \
> +		--export-width=$$s --export-height=$$s qemu.svg ; \
> +	done
> +	convert qemu_32x32.png qemu_32x32.bmp

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-01-10 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-10 12:00 [Qemu-devel] [PATCH v2 0/3] Fix & improve icon display on GTK and SDL frontends Daniel P. Berrangé
2019-01-10 12:00 ` [Qemu-devel] [PATCH v2 1/3] ui: install logo icons to $prefix/share/icons Daniel P. Berrangé
2019-01-10 15:00   ` Eric Blake [this message]
2019-01-11  5:46     ` Gerd Hoffmann
2019-01-10 12:00 ` [Qemu-devel] [PATCH v2 2/3] ui: fix icon display for GTK frontend under GNOME Shell with Wayland Daniel P. Berrangé
2019-01-10 12:00 ` [Qemu-devel] [PATCH v2 3/3] sdl: add support for high resolution window icon Daniel P. Berrangé
2019-01-11 10:43 ` [Qemu-devel] [PATCH v2 0/3] Fix & improve icon display on GTK and SDL frontends Gerd Hoffmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=c471db17-bab0-21e7-d8c2-7f1b8c1ef742@redhat.com \
    --to=eblake@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).