From: "Amavect ." <amavect@gmail.com>
To: 9front@9front.org
Subject: whiteboardfs collaborative drawing tools
Date: Sun, 12 Apr 2020 15:20:23 -0500 [thread overview]
Message-ID: <CAGOW0YM6o=M5=yVAjZRaFqozOccjO321jAzLc8=Rxa+N2a9J8Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
A daemon has been corrupted by the Commodore 64 in 9front city!
[lildev_corrupted.png]
Start the color picker...
HEY!
Build the color picker:
https://git.sr.ht/~amavect/makeu
https://git.sr.ht/~amavect/pal
https://git.sr.ht/~amavect/whiteboardfs
and off to the rescue!
Prepare the dryerase client, select the color red, and make the rescue!
[lildev_fixed.png]
The new collaborative drawing collection from 9front city!
whiteboardfs(4) is a collaborative drawing file server.
dryerase(1) is a client for whiteboardfs, updating with any live changes.
makeu(1) is a color picker.
pal(1) is a color palette.
You can run whiteboardfs locally by doing:
whiteboardfs
dryerase -c
/mnt/whiteboard/canvas.bit can also be used with page(1) and paint(1).
There is a public whiteboardfs instance:
srv tcp!66.42.112.142!2020 amaboard /mnt/whiteboard
It can be slow to load over long distances.
To try out pal(1) with dryerase(1):
Comment out the execl call in for makeu in whiteboardfs/dryerase.c
Uncomment the execl for pal.
I would have saved this for iwp9, but that's too far away now.
Please send bugs, crashes, and patches.
Thanks,
Amavect
[-- Attachment #2: lildev_corrupted.png --]
[-- Type: image/png, Size: 68880 bytes --]
[-- Attachment #3: lildev_fixed.png --]
[-- Type: image/png, Size: 42576 bytes --]
next reply other threads:[~2020-04-12 20:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 20:20 Amavect . [this message]
2020-04-14 1:23 ` [9front] " sl
[not found] ` <3BBC879D3A78F32E963ECCE7E2AEF8FA@ewsd.inri.net>
2020-04-14 21:59 ` Amavect .
2020-04-15 1:42 ` Stanley Lieber
2020-04-16 14:51 ` Ethan Gardener
2020-04-17 0:49 ` Amavect .
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='CAGOW0YM6o=M5=yVAjZRaFqozOccjO321jAzLc8=Rxa+N2a9J8Q@mail.gmail.com' \
--to=amavect@gmail.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).