From: Jacob Moody <moody@posixcafe.org>
To: 9front@9front.org
Subject: Re: [9front] [PATCH] rio: resize border and scrollbar based on font
Date: Fri, 10 May 2024 09:20:19 -0500 [thread overview]
Message-ID: <20c6b814-9c4c-469c-86fe-a86022c2f210@posixcafe.org> (raw)
In-Reply-To: <B80E34E0-F432-4B1B-AE52-29F582E049E9@stanleylieber.com>
On 5/10/24 09:16, Stanley Lieber wrote:
> On May 10, 2024 10:10:29 AM EDT, Jacob Moody <moody@posixcafe.org> wrote:
>> On 5/10/24 01:20, Kurt H Maier wrote:
>>> On Thu, May 09, 2024 at 07:14:06PM -0500, Jacob Moody wrote:
>>>>
>>>> we do not currently do any sort of scaling in the UI for larger displays.
>>>> I think we should be looking at a more general solution to this problem,
>>>
>>> scrollbars and borders should be arguments passed to rio and then
>>> exposed in env or elsewhere
>>>
>>> every other attempt at 'general solutions' to ui scaling have been
>>> miserable goddamn failures and I really really don't want to live
>>> through it again
>>>
>>> khm
>>
>> Alright then where's you're code for a solution here? I don't
>> want arguments to every fucking program for scaling.
>>
>>
>
> rio provides the borders, so every program in that rio that uses rio's borders would inherit the same settings.
>
> sl
There are assumptions about the window size in other places of the code, that's what I was talking about.
Look at /sys/include/draw.h:/BorderWidth/, there is code that currently relies on it being 4 pixels as a constant.
next prev parent reply other threads:[~2024-05-10 14:22 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
2024-05-10 6:13 Romano
2024-05-10 13:27 ` Kristo
2024-05-10 14:01 ` Stanley Lieber
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
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=20c6b814-9c4c-469c-86fe-a86022c2f210@posixcafe.org \
--to=moody@posixcafe.org \
--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).