all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: sirgazil <sirgazil@zoho.com>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>, "Ludovic Courtès" <ludo@gnu.org>
Cc: 34886@debbugs.gnu.org
Subject: bug#34886: [Web page] Screenshot alignment (and listing?)
Date: Sun, 17 Mar 2019 11:30:06 -0500	[thread overview]
Message-ID: <276bd200-2fdf-f093-058b-07c98e898f8f@zoho.com> (raw)
In-Reply-To: <875zsh1ozl.fsf@nckx>

El 17/03/19 a las 10:48 a. m., Tobias Geerinckx-Rice escribió:
> Ludo',
> 
> Ludovic Courtès wrote:
>> Tobias Geerinckx-Rice <me@tobias.gr> skribis:
>>
>>> The full-sized screenshots at
>>> https://www.gnu.org/software/guix/screenshots/gnome/ look awkwardly
>>> left-aligned to me[0].
>>>
>>> Is this intentional?  A browser bug?  This is in Icecat 60.5.1 on Guix
>>> System.
>>
>> The problem is that this secreenshot that I added a couple of days ago
>> has a ratio of 4/3 instead of 16/9 (I think?).
> 
> While true (I noticed that too), that's not the problem here.  The image 
> above is 16:something, but still isn't centred.  And even so, …

Yeah, that was a lazy/running-out-of-time design that expected all 
full-size screenshots to be full HD, and fill the whole screen 
horizontally for most people :P


>> Alternately, or in addition to that, it’d be great if the web site would
>> automatically do the right thing regardless of the aspect ratio of the
>> screenshot.  WDYT, sirgazil?
> 
> …my thoughts exactly :-)


I'll redesign it :)





-- 
Luis Felipe López Acevedo
http://sirgazil.bitbucket.io/

  reply	other threads:[~2019-03-17 16:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-16 19:22 bug#34886: [Web page] Screenshot alignment (and listing?) Tobias Geerinckx-Rice
2019-03-17 15:33 ` Ludovic Courtès
2019-03-17 15:48   ` Tobias Geerinckx-Rice
2019-03-17 16:30     ` sirgazil [this message]
2019-03-18 18:34     ` sirgazil
2019-03-22 20:19       ` Ludovic Courtès
2019-03-28 12:48       ` Tobias Geerinckx-Rice

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=276bd200-2fdf-f093-058b-07c98e898f8f@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=34886@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=me@tobias.gr \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.