9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: resize border and scrollbar based on font
Date: Fri, 10 May 2024 10:01:17 -0400	[thread overview]
Message-ID: <2D1BB646-F070-4E3F-B963-3748C82FA77C@stanleylieber.com> (raw)
In-Reply-To: <1626b2be-8b05-45cc-9266-bb7a4f6b7076@gmail.com>

On May 10, 2024 9:27:50 AM EDT, Kristo <kristo.ilmari@gmail.com> wrote:
>On 10.5.2024 9.13, Romano wrote:
>> I also can't imagine trying to go through all programs to see which
>> rely on a specific rio border-width.
>
>Rio was probably the first 9 program that I ever hacked on and I do recall
>that modifying the border size did unfortunately mess up some programs. If
>I had to guess now I'd say it was mothra. A lot of code has changed since
>then though, sorry I don't have a machine to test with at the moment.
>
>Kristo
>

mycroftiv's grio has border widths implemented as command flags. i remember seeing some weird behavior around the edges of some programs when i used it to diddle those values.

if existing programs rely on bad assumptions, it's worth adjusting them to remove the bad assumptions. sometimes you just have to do this, even though it can be a lot of tedious work.

that's why it's also worth figuring out where the best place to cut is. one of plan 9's strong suits has always been careful choices about what to omit, with various small pieces thoughtfully interacting to maximum effect, sometimes going too far, and sometimes not going far enough. the important thing is to think before cutting.

my experience with general scaling is that it seems nice when the physical screen geometry and the desired resolution don't result in a fuzzy mess, but this doesn't happen very often. specifying border size alone on the command line doesn't address all the other bibs and bobs like menus and scrollbars (fortunately,  rio isn't overly ornate). and of course, many programs manage their own unique scrollbars, menus, fonts, etc., usually hardcoded.

i can't help but admire the choice of cuts in sigrid's /dev/theme. if gui programs were modified to honor this convention, they wouldn't need to be altered again in the future. and a theme file seems like a good place to get specific about border sizes, etc. for example, the stuff phil9 has been woking on (mongrel, vdir, etc.) already honor /dev/theme.

alternately, maybe we need some kind of heuristic based on screen resolution? this would probably not make everybody happy, either, but might get us close enough to subjective visual consistency to call the game.

sl

  reply	other threads:[~2024-05-10 14:03 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-10  6:13 Romano
2024-05-10 13:27 ` Kristo
2024-05-10 14:01   ` Stanley Lieber [this message]
2024-05-10 14:17 ` Jacob Moody
2024-05-10 18:43   ` Romano
2024-05-10 19:15     ` Jacob Moody
2024-05-10 19:40       ` ori
2024-05-11 16:45         ` hiro
2024-05-11  4:31       ` Romano
2024-05-11 15:00         ` Jacob Moody
2024-05-11 16:54           ` hiro
2024-05-13  5:18           ` Romano
2024-05-11 16:42       ` hiro
2024-05-10 21:00     ` sl
2024-05-11  4:34       ` Romano
2024-05-13  5:38         ` Romano
  -- strict thread matches above, loose matches on Subject: below --
2024-05-09 21:04 Romano
2024-05-10  0:14 ` Jacob Moody
2024-05-10  0:34   ` sl
2024-05-10  6:20   ` Kurt H Maier
2024-05-10 14:10     ` Jacob Moody
2024-05-10 14:16       ` Stanley Lieber
2024-05-10 14:20         ` Jacob Moody
2024-05-10 14:23           ` Stanley Lieber
2024-05-10 14:21         ` ori
2024-05-10 14:33           ` Stanley Lieber
2024-05-10 14:37             ` Stanley Lieber
2024-05-10 14:58       ` Kurt H Maier
2024-05-10 15:28         ` Stuart Morrow
2024-05-10 16:11           ` Stanley Lieber
2024-05-10 16:43             ` Stuart Morrow
2024-05-10 16:50               ` Stuart Morrow
2024-05-11 16:36               ` hiro
2024-05-11 16:30             ` hiro
2024-05-11 16:27       ` hiro
2024-05-11 16:36         ` Jacob Moody

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=2D1BB646-F070-4E3F-B963-3748C82FA77C@stanleylieber.com \
    --to=sl@stanleylieber.com \
    --cc=9front@9front.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).