From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Bounties
Date: Thu, 16 Jan 2020 18:05:59 +0000 [thread overview]
Message-ID: <4b433d2c-5f3c-4288-9435-b20ce574aeee@www.fastmail.com> (raw)
In-Reply-To: <CAK8RtFpCs7QirqJiP5mAD3GftNW8jC29F0tLK=vuka5jBzD2oA@mail.gmail.com>
On Sun, Jan 5, 2020, at 7:06 AM, Jens Staal wrote:
> [2] A bar for the i3-like rio replacement with useful info = 30 €
>
> Some info that should be possible to display: workspaces, system info (cpu load,
> memory load, network load, ...), digital 24h clock. If not configurable, the bar
> should be at the top of the screen on all work spaces.
I wouldn't make this as described, it's making extra code with a different interface for no reason; very un-9ish. ;) Instead, I'd make a text field or a window. The text field would be linked to a writeable file, similar to writeable /dev/text. A script could write to it, as I once did in Rio to display time and battery while 9vx was full-screen. (If /dev/text had been writeable, it would have been perfect.)
The window would be a superset of this. A command to the window manager would start a program with the bar as its window. A script could write text to /dev/text or a graphical program could run in it. It's very easy to make a graphical program for that sort of task, or Rio could be patched to run multiple programs in the bar.
next prev parent reply other threads:[~2020-01-16 18:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-05 7:06 Bounties Jens Staal
2020-01-16 18:05 ` Ethan Gardener [this message]
2020-01-17 0:47 ` [9front] Bounties sl
2020-01-16 18:51 ` Calvin Morrison
2020-01-16 19:35 ` Calvin Morrison
2020-01-16 23:03 ` Ethan Gardener
[not found] <FEFDF1EDDEF96554EC8D099B3EFFBCE2@ewsd.inri.net>
2020-01-17 0:57 ` umbraticus
[not found] <134490038A9377D966659F986F257F34@ewsd.inri.net>
2020-01-17 14:43 ` Ethan Gardener
2020-01-17 16:05 ` kvik
2020-01-17 21:55 ` Silas McCroskey
2020-01-21 8:37 ` Ethan Gardener
2020-01-22 17:04 ` Ori Bernstein
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=4b433d2c-5f3c-4288-9435-b20ce574aeee@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).