9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Willow Liquorice <willow@howhill.com>
To: 9front@9front.org
Subject: Re: [9front] Blie - blended layers image editor
Date: Sun, 11 Aug 2024 15:01:37 +0100	[thread overview]
Message-ID: <744bec49-d4e0-41eb-b65a-a9c8962f1b6b@howhill.com> (raw)
In-Reply-To: <114c6958-8f2b-475a-9860-3036b7d32d8b@sirjofri.de>

May I make a suggestion? Take after, or somehow integrate this with, acme.

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.

Just being able to draw/type a brush into existence would be a breath of 
fresh air.

	- Willow

On 11/08/2024 10:18, sirjofri wrote:
> 11.08.2024 05:41:56 sl@stanleylieber.com:
>> hey, this puts pixels on the screen!
> 
> Sadly, only on the screen, yet :)
> 
> Directly after announcing I also added the first tool buttons for better visibility. Just in case, a short introduction for users:
> 
> Each layer has a type, and each type has its own editor. Bitmap p9images are one type, others aren't implemented yet, but planned.
> 
> When clicking on one layer, the editor for that layer will "open". That means that input is directed to that editor, and visualizations will be drawn from that editor. Also, the tools panel will open with the controls for this editor.
> 
> The p9image editor currently only has three buttons, more will follow for brush settings and color palette. Button "C" will change the drawing to display the final composited image (which is the standard), button "S" (solo) will display only the image of that layer, and button "M" will display the mask for that layer (if available). When displaying the mask, you can only draw on the mask. (I want more control over this so you can paint on the mask while displaying the full composited image).
> 
> The layers window currently has a weird ordering, because it's from top to bottom. That will change to the standard well-known stack (from bottom to top) in the future. Also, I want to include some micro-toolbar into the layers window for the editor to fill, so the buttons that are in the standard tool right now will probably be there at some point.
> 
> In general, there are a few points that are more important right now:
> 
> - zooming is slow. That should be improved.
> - saving is not yet possible, but is important, obviously.
> - adding and moving layers, as well as deleting.
> 
> sirjofri

  reply	other threads:[~2024-08-11 14:03 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 [this message]
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
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=744bec49-d4e0-41eb-b65a-a9c8962f1b6b@howhill.com \
    --to=willow@howhill.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).