The question is in the title:
“Is GIMP3.0 going to make all the Python2 scripts’ functionality lost with Linux OSs’ move to Python3 part of the new core?”
A followup: “And why not?” :^)
So–very–much work went into their development, and they have come to be relied on by so many, it would be a shame to see them abandoned.
The question is more about moving the functionality into GIMP’s core functionality than how to update scripts.
Q. Is there a process in GIMP development for looking at scripts’ capabilities and deciding whether that same functionality should be offered in GIMP out-of-the-box (eliminating the need for a script)?
Once 3.0 RC1 is released, the public API will be stable and people will be able to port their plug-ins with confidence that there won’t be breaking changes (in fact, that’s one of the last remaining hold-ups. We’re receiving the API to make sure we haven’t missed anything needed). We’re hoping that more people will start porting their Python 2 plug-ins. We’re also updating our documentation to make it easier to figure out how to do that.
You can check the “official” Python plug-ins for examples, but now you can do something like procedure.add_choice_argument () to add a dropdown/combobox or radio frame.
Hi! Yes, I think gimpfu is, but now Python uses the same API as the C plug-ins. You can see examples of how the UI works now in the /plug-ins/python/ folder: plug-ins/python · master · GNOME / GIMP · GitLab
Of course, you can also make your own GTK GUI if you want. We’ll be making more detailed tutorials once 3.0 RC1 is released and we have a minute to work on things besides the code.