From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] Blie - blended layers image editor
Date: Sun, 11 Aug 2024 20:43:55 +0200 (GMT+02:00) [thread overview]
Message-ID: <48f134dd-653d-4330-896e-9198271b8e5c@sirjofri.de> (raw)
In-Reply-To: <08f49d17-8763-4221-b8e6-6ed0dc468572@fjrhome.net>
11.08.2024 20:13:18 Frank D. Engel, Jr. <fde101@fjrhome.net>:
> It might be interesting to turn the core of the editor into a file server (in addition to its on-screen interface).
Interesting thought.
> Have a directory with files representing the individual layers so they can be edited directly using outside tools and scripts.
Actually, that's what it looks like in the on-disk file format. Nothing prevents you from editing the individual layers in these folders, that's what I do for testing.
> Have another for brushes (categories of brushes as subdirectories under the "brushes" directory, etc.).
That's also planned. It's possible I'll have to change the current layout a bit though.
> Find some way to represent tools as files you can write commands to or something perhaps...
Interesting idea. The question is, do we need that? At the moment I can just edit all the files as they are: the layer files, the layer config, in the future also the brushes and the brush settings. You just can't change that on the fly.
sirjofri
next prev parent reply other threads:[~2024-08-11 18:45 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 [this message]
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=48f134dd-653d-4330-896e-9198271b8e5c@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).