From: ori@eigenstate.org
To: sl@stanleylieber.com, 9front@9front.org
Subject: Re: [9front] mothra: proposal
Date: Thu, 19 Mar 2020 20:00:23 -0700 [thread overview]
Message-ID: <130A2579098A9D00FD34FFDA8EE1ED9C@eigenstate.org> (raw)
In-Reply-To: <C85FC655E82FCBE5B94289CB1073F9CC@ewsd.inri.net>
I'll split this into separate patches for separate review/testing,
and we can decide how to proceed change by change. It's going to
take me a few days.
>> I'm mostly ok with this, though I'm not a big fan of losing the
>> "command" vs "body" visual distinction.
>
> there are still a couple of lines separating those sections:
>
> http://plan9.stanleylieber.com/mothra/img/20200319.png
>
> but i'm not opposed to tweaking this. my biggest desire is to
> minimize the ui's decoration, and emphasize the content.
I'll post a tweaked version, keeps the bluegreen background
for the url section, and removes the lines between the menu
items.
>> 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'm not capable of implementing this. also, by this logic we'd
> need to change existing behavior of rio ad vt. would we delete
> the existing flags? i'm not married to -b, but i'm also not
> advocating full-blown theming. (fwiw, i also don't quite
> understand the vehement objection to it; standardizing it
> in one library seems like the right approach.)
I think you underestimate yourself. And, yes, if we have a
"dark mode", I'd want to remove '-b'.
> caveat:
>
> mothra sometimes only knows relative urls (because some web
> pages only offer relative urls as links), and relies on webfs
> to figure out the correct request to match whatever it clicks
> on. this sometimes breaks plumbing, as i implemented it.
>
> sl
Mm. we can probably read the 'parsed/url' before plumbing, but
I'm more interested in being able to plumb non-url text from
the page.
next parent reply other threads:[~2020-03-20 3:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C85FC655E82FCBE5B94289CB1073F9CC@ewsd.inri.net>
2020-03-20 3:00 ` ori [this message]
2020-03-20 3:21 ` Stanley Lieber
2020-03-20 5:04 ` umbraticus
[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
[not found] <F33C8113101B37111E4E412220D1377D@ewsd.inri.net>
2020-03-21 11:27 ` Ethan Gardener
2020-03-19 13:24 Stanley Lieber
2020-03-19 22:48 ` ori
2020-03-20 1:27 ` 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=130A2579098A9D00FD34FFDA8EE1ED9C@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).