Skip to content

Roadmap for resynthesizer to Gimp 3 #125

@bootchk

Description

@bootchk

This describes forthcoming work on resynthesizer.

The goal is: work in Gimp 3.

  1. build with meson
  2. outer plugins in scriptfu/scheme
  3. replace control panel plugin that uses C/Gtk with a scheme plugin
  4. restructure/rename files and directories

I started a new branch resynthesizer3, from the deprecations branch. The first commit minimally proves the goal.

Discussion

Meson: Gimp 3 only builds with meson. Meson is much better. Resynthesizer3 will only build with meson.

ScriptFu scripts (with few changes) will still work in Gimp 3 whereas Python2 GimpFu plugins are more difficult to port to Gimp 3. GimpFuv3 is a possible alternative but it has little traction yet and is just another dependency. But itr-tert has already ported the resynthesizer plugins back to Scheme. Resynthesizer for Gimp 3 will use them.

The control panel in C/Gtk2 is just a dialog that passes args on to the resynthesizer engine plugin. It offers minimal added value, just small user-friendliness insuring the entered args are consistent with the requirements of the engine plugin. A ScriptFu plugin can more easily do the same thing, except for the user-friendliness. A ScriptFu plugin is not dependent on deprecated Gtk2, requires no build, and can be more easily maintained. Users of the control panel are expected to have deep knowledge of the engine, and from now on will be expected to ensure entered args are consistent, without aid from the user interface.

The reorganization of the source will more clearly indicate the architecture.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions