This is a way to use Gegl operations in a sequential way (after reading the discussion in this thread).
I don't know of a way to interactively call individual Gegl filters sequentially from a Python plugin.
This plugin will execute several Gegl operations (not interactive) sequentially with default values.



After executing the plugin, now you can call a particular filter from the layers dock and edit its parameters and change the order of filter execution or disable them:


After editing (changing) the filter parameters, you can save them (under an appropriate name) for possible reloading (for use as so-called presets):


or export (if you want to share your settings):


In menu: Filters ➤ Multi Gegl

One Gegl filter is just 4 lines of code which you can easily change (delete or add filters) to call other Gegl operations and/or filters LinuxBeaver.

This plugin is just an example (a bit like a Composer) but by far the simplest solution is to use BATCHER.

The advantage of the multiGegl.py plugin (or rather fx) is the direct preview on canvas and the ability to use 'Presetss' or 'Import Current Settings' from a file.

Why not just make a empty layer group .xcf file with these three filters and drag and drop it into the canvas then put the content you want inside it?

or

Why not import a batcher preset? That does the same thing, I'm just saying. What works for you works for you.

As I wrote that Batcher is the simplest (best) solution - but not always.
Maybe try adding gegl: threshold as 'Add Custom Action'.
You will get this error:


It's a bit confusing but in Python code you should use gimp:threshold (which Batcher can't know about).

Batcher is also not the fastest solution because it works twice (separately for preview and result, which can also give a different final result than in the preview, but also G'MIC works the same way).

Operating on a group of layers is very cool but to share the result with others it requires sending a file saved as XCF (which you often suggest but somehow I haven't found examples).

Your other idea of ​​creating a separate Gegl filter from these operations is probably just another (unfortunately not very effective) incentive for others (and modifying the Python plugin is much easier).

Regarding GIMP name space
https://github.com/kamilburda/batcher/issues/85

Regarding .xcf file. Try opening this and typing text in it.

and below the text put an empty layer with no content so it doesn't clip. I can't add the empty layer because I don't know the canvas size.

Thank you for the XCF example.
Maybe we'll see a separate thread with such files.
Objectively, it's the easiest way.
However, I appreciate (prefer) the ability to invoke the plug-in from the Gimp menu.
Great that at your request, Batcher will have even more options.

I was directed to a very well explained (described) plugin by quietreader in another thread.

How to Write Python Plug-ins for GIMP 3 by Kamil Burda:
https://medium.com/@kamilburda/how-to-w ... b81fc2c98d
Download https://gist.github.com/kamilburda/320b ... 0f3e21f1fb



In menu: Filters ➤ Artistic ➤ Sketchify
However, in this example, fx operations are not available by using: 'image.merge_down'.

In the attached version, I added an option to use this command?


In menu: Filters ➤ Artistic ➤ Sketchify fx...

Here is GEGL syntax to do sketchify





Please note gegl:dst-over is the behind blend mode
and gegl:over is the normal blend mode

Here are the nodes defined with custom names, notice how gegl:color-to-alpha is named c2a
and cloudy is short for gegl:noise-solid, that's because we can name them whatever we want




Now lets define the property redirects



Now lets define the properties



Now lets write the defined GEGL Graph



Before I explain, keep in mind blend modes in GEGL have unique abilities such as storing multiple filters or other blend modes inside them something GIMP cannot do. And this case does exactly that


What's going on?

The first three GEGL nodes gegl:edge-neon, gegl:color-to-alpha and gegl:color-overlay are being applied linearly but then a behind blend mode is introduced after gegl:color-overlay, Inside the behind blend mode is gegl:color, then a unique GEGL feature that GIMP does not have happens, a following node representing the normal blend mode is put inside the behind blend mode, a blend mode inside a blend mode, and keep in mind each blend mode can store infinite nodes.

The normal blend mode (gegl:over is put inside the behind blend mode (gegl:dst-over)

Put in the simplest way possible



In this filters case behind blend mode has a gegl:color and behind blend mode in it, but remember the normal blend mode can also have content in it to.



And indeed it does have content, the normal blend mode has gegl:noise-solid inside it followed by a gegl:opacity to make it mostly transparent at 15% opacity.

So explained simply, we have an edge detect, color to alpha and color overlay applied linear, Then the behind blend mode instructs gegl:color to fill behind the edge extract while also housing a gegl normal blend mode for the solid noise and gegl opacity exist within normal so solid noise has an opacity slider.


Now lets wrap things up with the title and description



I'm telling you its worth time to learn GEGL syntax and make true GEGL plugins. 95% percent of what you need to make this a plugin is here, the only thing I didn't do is put it in the correct order and file name

1. first comes property list
2. then comes node definitions
3. then comes the defined graph
4. then comes property redirects
5. then comes title and description

1.5 is where you put the filename, c file name and other few things I excluded.

I wonder if someone will figure out how to convert this to a plugin. If they do it will have two color pickers, edge amount slider and a slider for and button for the solid noise

I completed the plugin renaming it "edge detect theories" to show off various types of edge detect artistic styles. I did not do this because of benevolence but because I myself had self interest in it and added new features. I credited Kamil Burda for parts of it they found, but keep in mind I made original modifications to the GEGL graph. Myself as someone who doesn't believe in IP means anyone is welcome to modify my plugin and make it better or worse if they want to tinker.

Once again partial credit goes to Kamil Burda for discovering a large part of the graph
(even though my 2022 edge extract does something similar)


















LOCATION TO PUT BINARY

Windows

C:\Users\(USERNAME)\AppData\Local\gegl-0.4\plug-ins

Linux

~/.local/share/gegl-0.4/plug-ins

Linux (Flatpak includes Chromebook)

~/.var/app/org.gimp.GIMP/data/gegl-0.4/plug-ins

--