From: ori@eigenstate.org
To: sl@stanleylieber.com, 9front@9front.org
Subject: Re: [9front] mothra: proposal
Date: Thu, 19 Mar 2020 15:48:39 -0700 [thread overview]
Message-ID: <4683315B9C3DE021CEF6ED7969DA706A@eigenstate.org> (raw)
In-Reply-To: <B4522F48-E59F-45B2-B880-8716A418BBDD@stanleylieber.com>
> On March 18, 2020 7:49:16 PM EDT, sl@stanleylieber.com wrote:
>>i've been maintaining forks of mothra for years. i don't anticipate
>>making more big changes any time soon, and i have zero time to
>>continue applying the changes from 9front to my several forks.
>>
>>i propose to backport the following changes from my forks to 9front:
Thanks for doing the work. I'll take a look at the code soon,
but a first set of comments after testing it out:
>> 1.) restore original default fonts.
>> a.) our dejavusans is fuzzy as hell, and it sucks.
>> 1.) users can easily choose their own fonts
>> and
>> recompile.
Hm. It looks fine on my screen -- but, sure.
>> 2.) backport my changes to libpanel to remove useless panel
>> borders and fake shadow lines. stop underlining hyperlinks,
>> and instead make them blue.[0][1]
>> a.) perhaps in a saner manner.
>> 1.) currently, lines, borders, bullet points,
>> etc., are defined in all sorts of different
>> places, not even entirely inside of libpanel.
>> i made no attempt to address this. in rio,
>> we ended up putting all the color definitions
>> into one file, for easy modification.
I'm mostly ok with this, though I'm not a big fan of losing the
"command" vs "body" visual distinction. I also see lines drawn
between menu items. I may want to tweak it a bit more to match
the look of rio/sam windows.
>> 3.) implement -b flag for dark mode, white-on-black text.[2]
>> a.) similar to rio -b, and vt -b.
>> 1.) users are free to implement any desired
>> schemes beyond default and -b by configuring
>> the included .c files.
I don't like theming, but I like the propagation of dark mode
flags even less. If we want this, libdraw needs to signal to
programs which colors they should use, without a '-b' flag.
I know that this way lies bikeshedding. *sigh*.
>>caveat: i do not have a lot of faith in my own ability to backport
>>these changes cleanly.
>>
>>volunteers are welcome.
>>
>>sl
>>
>>[0] http://plan9.stanleylieber.com/src/mothra.white.tgz
>>[1] http://plan9.stanleylieber.com/src/mothra.black.tgz
>>[2] http://plan9.stanleylieber.com/mothra/img/20200310.png
Sending this out in the form of patches would make it easier
to see what's changed.
> forgot:
>
> 4.) plumb menu item.
>
> sl
The plumb menu is a definite yes from me.
next prev parent reply other threads:[~2020-03-19 22:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 13:24 Stanley Lieber
2020-03-19 22:48 ` ori [this message]
2020-03-20 1:27 ` sl
[not found] <C85FC655E82FCBE5B94289CB1073F9CC@ewsd.inri.net>
2020-03-20 3:00 ` ori
2020-03-20 3:21 ` Stanley Lieber
2020-03-20 5:04 ` umbraticus
[not found] <F33C8113101B37111E4E412220D1377D@ewsd.inri.net>
2020-03-21 11:27 ` Ethan Gardener
[not found] <42A469F0BBA88991B13EB7B76C0079B3@ewsd.inri.net>
2020-04-12 19:16 ` ori
2020-04-12 19:21 ` ori
2020-04-12 19:42 ` Stanley Lieber
2020-04-13 0:43 ` sl
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=4683315B9C3DE021CEF6ED7969DA706A@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=sl@stanleylieber.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.
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).