From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: Vincent Legoll <vincent.legoll@gmail.com>,
Ricardo Wurmus <rekado@elephly.net>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Document our WIP
Date: Sat, 27 Mar 2021 17:50:45 +0100 [thread overview]
Message-ID: <efdab65ccdcf2e23b49a67daf3a33a89c54b0bd4.camel@zaclys.net> (raw)
In-Reply-To: <HjUF-Q76VClLdhSs88kR1uhlOlg46RJxQs152qKVO4DrDHNxIizc3Mkn4oXhJfnTZ8VnRJ7_20uZvcJK1Rc12Q-1EfBGw__3namos0_PItM=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1072 bytes --]
On Sat, 2021-03-27 at 16:42 +0000, Luis Felipe wrote:
> I'm fine with that too (for now). I can send that patch.
>
> The reason I didn't suggest that, though, is that the primary menu
> has already grown too big in my opinion. And, with the current
> design, the visibility of the primary menu changes depending on
> screen width: The primary menu is hidden behind a primary menu button
> for screens narrower than 920 px (which may be too soon already).
>
> So, adding more primary items to that menu means the menu has to be
> hidden for even wider screens than 920. An that's from the English
> point of view only; I haven't checked how the header bar is behaving
> for other locales...
>
> That said, I have a pending proposal to redesign the header bar to
> behave similar to headers in GNOME desktop applications (it could be
> simpler and follow already used conventions that people may be
> familiar with).
After looking more closely at the help page, I think it could be
acceptable to have it there too. But is the wiki an help resource?
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-27 16:51 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-27 10:07 Document our WIP Vincent Legoll
2021-03-27 14:20 ` Léo Le Bouter
2021-03-27 14:44 ` Ricardo Wurmus
2021-03-27 15:32 ` Joshua Branson
2021-03-27 15:34 ` Léo Le Bouter
2021-03-27 15:44 ` Luis Felipe
2021-03-27 15:54 ` Léo Le Bouter
2021-03-27 15:41 ` Vincent Legoll
2021-03-27 15:50 ` Vincent Legoll
2021-03-27 15:54 ` Luis Felipe
2021-03-27 16:03 ` Vincent Legoll
2021-03-27 16:04 ` Léo Le Bouter
2021-03-27 16:42 ` Luis Felipe
2021-03-27 16:50 ` Léo Le Bouter [this message]
2021-03-27 17:02 ` Luis Felipe
2021-03-27 17:05 ` Vincent Legoll
2021-03-27 18:12 ` Vincent Legoll
2021-03-27 18:18 ` Luis Felipe
2021-03-28 15:33 ` Vincent Legoll
2021-03-27 17:02 ` Vincent Legoll
2021-03-27 18:11 ` Luis Felipe
2021-03-27 18:13 ` Vincent Legoll
2021-03-27 16:01 ` Léo Le Bouter
2021-03-30 10:37 ` Ludovic Courtès
2021-03-31 17:52 ` Léo Le Bouter
2021-03-31 18:16 ` Leo Famulari
2021-04-01 21:33 ` Luis Felipe
2021-04-02 16:11 ` Léo Le Bouter
2021-04-08 19:55 ` Luis Felipe
2021-04-08 21:06 ` Vincent Legoll
2021-04-02 4:42 ` Gurjeet Singh
2021-04-05 23:35 ` Léo Le Bouter
2021-04-07 15:55 ` Vincent Legoll
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=efdab65ccdcf2e23b49a67daf3a33a89c54b0bd4.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=rekado@elephly.net \
--cc=vincent.legoll@gmail.com \
/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.