Oh yeah I forgot to mention I tried to make a plugin that called GMIC, I tried to make a plugin that mimicked resynthesizer and inpainted the color red, I tried to make a plugin that removed backgrounds, I tried to make a plugin that did Marero Q's request, I tried to make a plugin that did anisotropic smoothing, heart grids, ect... and all these ideas failed miserable.
Grok is the best AI for plugins. Deep Seek is the second best. They must be prompted at the start like
Before we begin it is important to follow these rules. We are writing GEGL plugin for GIMP, you can learn how to write GEGL plugins at https://github.com/GNOME/gegl/tree/master/operations/common . Our plugins name will be smooth.c and gegl:aiplugin No code will ever come after the class key area gegl_operation_class_set_keys(operation_class,
"name", "gegl:aiplugin",
"title", _("Windows 95 Desktop"),
"reference-hash", "windows95geglfair3",
"description", _("Renders a Windows 95-style desktop with a colored wallpaper and taskbar"),
NULL);
}
#endif For example you will modify the name title and description of the class key area but nothing will come after the #endif or inbetween the } When writing a GEGL plugin will you have a format like this #include "config.h"
#include <glib/gi18n-lib.h>
#include <gegl.h>
#include <gegl-plugin.h>
#ifdef GEGL_PROPERTIES
property_color(wallpaper_color, _("Wallpaper Color"), "0.0, 0.5, 0.5")
description(_("Color of the desktop wallpaper (default is teal)"))
property_color(taskbar_color, _("Taskbar Color"), "0.75, 0.75, 0.75")
description(_("Color of the taskbar (default is light gray)"))
#else
#define GEGL_OP_POINT_FILTER
#define GEGL_OP_NAME smooth
#define GEGL_OP_C_SOURCE smooth.c always, the properties may be different ranging from property_double property_int property_seed and property_color ect.. but they will always be in this format. Same with the #include libraries, there may be different ones but they will always be in that location. Remember the plugin has nothing to do with Windows 95, we are just using Windows 95 as an example. Soon we will make a GEGL plugin for GIMP I just want you to follow these parameters
Then tell them to make a plugin with 10 versions of itself in a drop down list. (So you get 10 questions in one) and remove all non-working/poor working versions and only leave one or the few that are the best. That is what I do to avoid the infamous vibe coders rate limit. I also attach working vibe coded files like `candyspiral.c` to show the AI the previous file that worked and instruct it to heavily modify the previous file to match the new request. Also start out simple and expand the plugin.
And they are only good at making pattern gradient and shape plugins. They are bad at anything to do with blurs, smoothing, inpainting, sharpening, tonemapping, 3d stuff, or anything fancy in that regard
Also off topic. GEGL Effects third birthday was May 12 2025.
Login
Register
Tweets
FAQ
Advanced Search
