Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Arrow Script
I tried to backport Arrow V3 latest version to Gimp 2.10, but I couldn't... this makes me think that it will be difficult to have old scripts updated for Gimp 3.0.

For the moment I have modified the V3 that I had backwards compatible with to support Gimp 2.99.18... it works but makes some errors, but if I solve them there will be no backwards compatibility.

Your Arrow v3 is definitely the best example of how you will need to modify your code to run on Gimp 3.0.

I hope the Gimp 3.0 developers realize that it is now very difficult to modify an old script and have backward compatibility.

Your way of having two versions is the only choice to not have complicated code.

Thank you!
Reply
(03-01-2024, 01:15 PM)vitforlinux Wrote: I tried to backport Arrow V3 latest version to Gimp 2.10, but I couldn't... this makes me think that it will be difficult to have old scripts updated for Gimp 3.0.

For the moment I have modified the V3 that I had backwards compatible with to support Gimp 2.99.18... it works but makes some errors, but if I solve them there will be no backwards compatibility.

Your Arrow v3 is definitely the best example of how you will need to modify your code to run on Gimp 3.0.

I hope the Gimp 3.0 developers realize that it is now very difficult to modify an old script and have backward compatibility.

Your way of having two versions is the only choice to not have complicated code.

Thank you!

Once GIMP 3.0 is released the need to have scripts for 2.10.x will fade. In order to gain the advantages of V2.99/V3 scripts they have to use script-fu-register-filter (instead of script-fu-register) so making having a single version of the script for all versions is a non-starter.
Reply
(03-01-2024, 04:59 PM)programmer_ceds Wrote: they have to use script-fu-register-filter (instead of script-fu-register)

Do you know where can we find a list of those changes?
Patrice
Reply
(03-02-2024, 04:46 AM)PixLab Wrote:
(03-01-2024, 04:59 PM)programmer_ceds Wrote: they have to use script-fu-register-filter (instead of script-fu-register)

Do you know where can we find a list of those changes?

Some information is given at:

https://developer.gimp.org/resource/scri...ter-plugin

But note that at least one of the links leads to a V2 example.

Generally looking at the scripts supplied with GIMP is as useful as anything. If you download the source code from https://gitlab.gnome.org/GNOME/gimp the scripts are in plug-ins/python and plug-ins/script-fu/scripts
Reply
(03-02-2024, 10:30 AM)programmer_ceds Wrote:
(03-02-2024, 04:46 AM)PixLab Wrote:
(03-01-2024, 04:59 PM)programmer_ceds Wrote: they have to use script-fu-register-filter (instead of script-fu-register)

Do you know where can we find a list of those changes?

Some information is given at:

https://developer.gimp.org/resource/scri...ter-plugin

But note that at least one of the links leads to a V2 example.

Generally looking at the scripts supplied with GIMP is as useful as anything. If you download the source code from https://gitlab.gnome.org/GNOME/gimp the scripts are in plug-ins/python and plug-ins/script-fu/scripts

Thank you especially the last one > https://gitlab.gnome.org/GNOME/gimp/-/tr...type=heads plenty to take a look at for the 2.99 / 3
Patrice
Reply
I have to say that I'm not a fan of backwards compatibility, but it's a way to have just one scm file for two versions... and avoid unnecessary error reporting.

For many, writing V3 (or 299 in my case) is not clear enough... but there is no solution, surely someone will want to put the files for Gimp 2.8 in 3.0.

Thanks again for the links to the development resources.
Reply


Forum Jump: