Let me just say the last four plugins I need to port to python are just background design plugins (starfield, star background starburst) and video degradration. All the important plugins have already been ported.

The most useful plugins for scripting IMO will be the text stylers "glossy balloon, sharp bevel, custom bevel, inner glow, long shadow pd, neon border" and align for positioning images anywhere. So they are done. Mission Accomplished. I'll get to the last four when I feel like it.


Update here contains a few parameter error fixes I made. No new plugins were added but metallic had an error I fixed. It works but it had a slider that went way above its limit.
https://github.com/LinuxBeaver/Special_ ... /releases/

This goes in

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

Linux
/home/(USERNAME)/.local/share/gegl-0.4/plug-ins

Linux (Flatpak includes Chromebook)
/home/(USERNAME)/.var/app/org.gimp.GIMP/data/gegl-0.4/plug-ins



This goes in the normal plugins directory

@contrast_
Just a thought:
Almost every "c" code contains an additional registration (except GEGL)
Gimp installation procedure
Have you tried adding them?
If successful, you can locate anywhere in the menu and I think without the need for additional registration.

This is the only way I know how to put filters in Gimp's main menu.


I'm not sure if I fully understand what you mean.

GEGL is now in Pixelitor and a similar rule to python GEGL applies here.

viewtopic.php?f=22&t=3247&p=286097#p286097

Any GEGL Plugin of mine that works in python will also work in Pixelitor and even some that use Gimp only name spaces do work in Pixelitor but Pixelitor will ignore the (gimp:) namespace and not load anything. Where as python will report an error and not run anything.

So for examle my custom bevel plugin works in Pixelitor with the hardlight blend mode that is (gegl:hard-light) but if it is changed to grain merge blend mode (gimp:layer-mode layer-mode=grain-merge) it will just load every operation but grain merge.

I am working on porting even more plugins of mine to python and pixelitor GEGL. Here is an example of a special build of my RING BEVEL plugin that was ported to work without any Gimp namespaces.

My Inner Glow plugin had an unreleased update that broke all python to gegl stuff for me. I am going to investigate why this happened. Thank God I didn't release the update.

I find it sad that GEGL plugins I make can effect someone else's plugin.

I updated my special GEGL plugins to work again with modern gegl without connect_from. Now all of these plugins are hidden from Gimp's GUI but do show up in the plugins registry (WHEN USED WITH THE .PY FILE)

https://github.com/LinuxBeaver/Special_ ... command.py

*update to remove layer shadow


also off topic, it is highly concerning that scripting GEGL in python is far more popular then chaining GEGL nodes the way I do. Python is not capable of chaining GEGL nodes correctly and most of the awesome stuff I do in GEGL is not possible in python or even CMYK Student's Gimp. This is because GEGL depends on nodes and composers that only GEGL Syntax can access.

The GEGL plugin script-layershadow.dll/so was causing a Gimp fail to start up issue when default layer shadow is present so it was removed.


Layer Shadow is an obscure plugin that I rarely talk about and it does not ship with anything. So there is a low chance anyone was affected by this. However Gimp will not start up until script-layershadow.dll or layershadow.dll is removed. I suggest removing script-layershadow.dll