Comments by "Lawrence D’Oliveiro" (@lawrencedoliveiro9104) on "GIMP 3 Is Coming In 2023... Probably" video.

  1. GIMP’s internal architecture is already structured that way. If you look at the plugin API, you see this thing called the “PDB” (procedure database) -- this is a registry of all GIMP’s operations, both builtin and provided by plugins. Not only can you invoke these operations from a plugin (that includes calling operations in one plugin from another plugin!), you can also type commands directly into the scripting console. Another nice thing is, this is scripting-language-independent. GIMP 2 provided an API for Python 2, but Python 2 is dead now. But I found a way to rewrap the API in Python 3 (see my pylibgimp2 project), and GIMP itself neithers knows or cares about the difference.
    2
  2. GIMP already uses GEGL for all its pixel manipulations. This copes seamlessly with a whole range of bit depths. This is why GIMP can natively handle EXR files with 32-bit floating-point pixel components, and Photoshop cannot.
    1
  3. GIMP already uses GEGL for all its pixel manipulations. This copes seamlessly with a whole range of bit depths. This is why GIMP can natively handle EXR files with 32-bit floating-point pixel components, and Photoshop cannot.
    1
  4.  @mskiptr  You can already do that. The API is object-oriented: PDB calls will return a reference to created objects, which you can then pass to other PDB calls. So you can write your entire image manipulation process as a series of script commands, in any supported language.
    1
  5.  @mskiptr  Do it the way I said.
    1
  6.  @mskiptr  But you can’t invoke GIMP operations with those libraries. Oh, you want GIMP to record a script for you as you invoke its operations? I think there are plugins for that.
    1
  7. I think the one that is not GIMP-specific is supposed to be called “GTK+”.
    1