If script-fu are placed in the "scripts" folder, they have a habitual and predictable behavior.
If I modify them and put them in "plugins" they have another one, changes must be added on purpose and sometimes you don't understand the mistake.
BUT if I put them in "plugins" Gimp 3.0 official appimage overcomes some problems that crash the script engine.
Now comes the problem, exactly like to be or not to be, I have to continue to use the "scripts" folder, or I have to arm myself and solve the problems it causes by moving them to "plugins".
I wouldn't want my "to be or not to be" to be Mel Brooks' film.
(03-01-2025, 01:02 PM)vitforlinux Wrote: If script-fu are placed in the "scripts" folder, they have a habitual and predictable behavior.
If I modify them and put them in "plugins" they have another one, changes must be added on purpose and sometimes you don't understand the mistake.
BUT if I put them in "plugins" Gimp 3.0 official appimage overcomes some problems that crash the script engine.
Now comes the problem, exactly like to be or not to be, I have to continue to use the "scripts" folder, or I have to arm myself and solve the problems it causes by moving them to "plugins".
I wouldn't want my "to be or not to be" to be Mel Brooks' film.
I think that long term you will have no option but to migrate to plug-ins. For this reason if you are modifying .scm scripts from GIMP V2 to V3 it may be better to bite the bullet now and convert them to V3 plug-ins.
(03-01-2025, 01:02 PM)vitforlinux Wrote: If script-fu are placed in the "scripts" folder, they have a habitual and predictable behavior.
If I modify them and put them in "plugins" they have another one, changes must be added on purpose and sometimes you don't understand the mistake.
BUT if I put them in "plugins" Gimp 3.0 official appimage overcomes some problems that crash the script engine.
Now comes the problem, exactly like to be or not to be, I have to continue to use the "scripts" folder, or I have to arm myself and solve the problems it causes by moving them to "plugins".
I wouldn't want my "to be or not to be" to be Mel Brooks' film.
I think that long term you will have no option but to migrate to plug-ins. For this reason if you are modifying .scm scripts from GIMP V2 to V3 it may be better to bite the bullet now and convert them to V3 plug-ins.
Except that bizarre errors come out, and things like script-fu-util.scm or script-fu-drop-shadow are not found... and what works then doesn't work.
And strangely enough, things that shouldn't work work, so you don't understand how to fix the rest.
The only thing to do is to ask the Gimp developers what future awaits us...
(03-01-2025, 01:02 PM)vitforlinux Wrote: If script-fu are placed in the "scripts" folder, they have a habitual and predictable behavior.
If I modify them and put them in "plugins" they have another one, changes must be added on purpose and sometimes you don't understand the mistake.
BUT if I put them in "plugins" Gimp 3.0 official appimage overcomes some problems that crash the script engine.
Now comes the problem, exactly like to be or not to be, I have to continue to use the "scripts" folder, or I have to arm myself and solve the problems it causes by moving them to "plugins".
I wouldn't want my "to be or not to be" to be Mel Brooks' film.
I think that long term you will have no option but to migrate to plug-ins. For this reason if you are modifying .scm scripts from GIMP V2 to V3 it may be better to bite the bullet now and convert them to V3 plug-ins.
Except that bizarre errors come out, and things like script-fu-util.scm or script-fu-drop-shadow are not found... and what works then doesn't work.
And strangely enough, things that shouldn't work work, so you don't understand how to fix the rest.
The only thing to do is to ask the Gimp developers what future awaits us...
I found an intermediate solution: the ones that will work both as plugins and as script-fu will have a P in the filename.
For example: 3D_WOOD_300_P.scm
However, the recommended location is in the scripts folder.
03-06-2025, 04:48 PM (This post was last modified: 03-06-2025, 04:49 PM by rich2005.)
(03-06-2025, 01:12 PM)vitforlinux Wrote: I had a precise answer: script-fu go in the scripts directory, there is no chance that they will go into plugins as far as Gimp 3.0 is concerned.
Not a 100% correct. The reply was: quote: At least for 3.0, I can assure you that the scripts folder will remain so you can say that for the user.
There is a Gimp 3.0 scripts folder, and you can write a file.scm that goes in the scripts folder and works as in Gimp 2.10
However
There are filename.scm written for script-fu-interpreter-3.0 that go in the Gimp 3.0 plug-ins folder, following the Gimp 3.0 requirement of: in a folder with the same name as the filename and for linux marked executable.
03-07-2025, 12:45 PM (This post was last modified: 03-07-2025, 12:47 PM by vitforlinux.)
The differences between script-fu in 2.10 without deprecate and 3.0 are comparable to the one between pasta with tomato sauce and pasta with pesto... The pasta is still there.
