From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Blie - blended layers image editor
Date: Sun, 11 Aug 2024 23:25:49 +0200 (GMT+02:00) [thread overview]
Message-ID: <96ee9069-04cf-411f-a562-1c23676624f6@sirjofri.de> (raw)
In-Reply-To: <EDD86EC08924E298B71B213C1B877CA6@gaff.inri.net>
11.08.2024 20:50:22 sl@stanleylieber.com:
> paint(1) has some nice design choices. following programs like sam
> and acme, you can do things like this:
>
> <command
> Executes command and reads the canvas from its standard
> output.
>
> >command
> Executes command and writes the canvas to its standard
> input.
>
> |command
> Transforms the canvas by piping it through command.
>
> this allows a lot of features to be towed outside the layer-compositing
> program entirely, and any such tools can also be reused for other
> applications.
Yes, exactly.
In blie, that should be easily doable as an effect/pipe layer, which would be a separate layer type that doesn't have any bitmap data itself, but pipes the image through any command (or commands) you'd like, for example a bloom filter.
The bonus would be that this is non-destructive, so you can adjust the base layers and still get the same effect added on it. You can also move that layer around, which changes the image, but you don't lose any data.
That's also the idea behind farbfeld (if you want to look at it): have an image format that's as simple as possible so you can send the data in a pipe. Farbfeld is not primarily designed as a storage format, more like an intermediate format: png2ff <src.png | filterA | filterB | ff2png >dst.png. (I don't plan to add farbfeld support as it's not a plan 9 thing. I built some ff to plan 9 image converter a while ago though.)
sirjofri
next prev parent reply other threads:[~2024-08-11 21:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 16:25 sirjofri
2024-08-11 3:40 ` sl
2024-08-11 9:18 ` sirjofri
2024-08-11 14:01 ` Willow Liquorice
2024-08-11 17:49 ` sirjofri
2024-08-11 18:10 ` Frank D. Engel, Jr.
2024-08-11 18:43 ` sirjofri
2024-08-11 18:49 ` sl
2024-08-11 21:25 ` sirjofri [this message]
2024-08-12 2:53 ` ori
2024-08-12 2:52 ` ori
2024-08-12 7:53 ` sirjofri
2024-08-12 8:37 ` ori
2024-08-15 21:19 ` sirjofri
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=96ee9069-04cf-411f-a562-1c23676624f6@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--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).