From: "Frank D. Engel, Jr." <fde101@fjrhome.net>
To: 9front@9front.org
Subject: Re: [9front] Blie - blended layers image editor
Date: Sun, 11 Aug 2024 14:10:00 -0400 [thread overview]
Message-ID: <08f49d17-8763-4221-b8e6-6ed0dc468572@fjrhome.net> (raw)
In-Reply-To: <8b15626b-efdb-4476-ade1-e6198befa62f@sirjofri.de>
It might be interesting to turn the core of the editor into a file
server (in addition to its on-screen interface).
Have a directory with files representing the individual layers so they
can be edited directly using outside tools and scripts.
Have another for brushes (categories of brushes as subdirectories under
the "brushes" directory, etc.).
Find some way to represent tools as files you can write commands to or
something perhaps...
Just a thought.
On 8/11/24 13:49, sirjofri wrote:
> 11.08.2024 16:03:18 Willow Liquorice <willow@howhill.com>:
>> May I make a suggestion? Take after, or somehow integrate this with, acme.
> I won't integrate this with acme, and I think it shouldn't be the same as acme. A few things will have some inspiration from it.
>
>> One thing I've found profoundly frustrating with featureful image editors (looking at you, Krita and GIMP) is the amount of menu diving one has to do to twiddle things, and the sheer quantity of "magic" in play. Nothing feels particularly obvious or consistent.
> Yeah, that's horrible indeed. I plan to do it as simple as possible, and also file-driven.
>
> Initially, I wanted to have all the data in a zip and you open the zip file for editing, but now I think it's probably better to just leave it as individual files. Those can still be zipped, and you can use source control more easily.
>
>> Just being able to draw/type a brush into existence would be a breath of fresh air.
> My current idea is to have "slots" for the brushes/colors and right-clicking them opens some kinda edit mode where you can just change its parameters (size, opacity, ...). For the colors you would get a color wheel or sliders. I'm also thinking about having shortcuts for a few parameters, so you can easily change the size of the brush without clicking around. In the end, I'll see where the project will lead.
>
> When there is something fully working (with saving etc) testers and feedback are welcome, as well as suggestions.
>
> sirjofri
>
next prev parent reply other threads:[~2024-08-11 18:13 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. [this message]
2024-08-11 18:43 ` sirjofri
2024-08-11 18:49 ` sl
2024-08-11 21:25 ` sirjofri
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=08f49d17-8763-4221-b8e6-6ed0dc468572@fjrhome.net \
--to=fde101@fjrhome.net \
--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).