plugin-py3-export-all

[CowboyJoe]

I was looking for a plugin that exports all open files at once. I tried several plugins, but not a single one worked for me in Gimp 3.04. Then I tried to modify a plugin written in Scheme, but failed miserably.

Then I decided to write one in Python myself. The result can be found here:
https://gitlab.com/CowboyJoe/plugin-py3-export-all
I develop on Linux and the plugin has some nice features I missed in other plugins. It still has a long Todo-list but I like it and it serves my needs.

A user who is using Windows told me the plugin does not work for her. Atm. I am not sure if the plugin was installed at the wrong location or the plugin just crahes.

Since I dont have Windows I downloaded Gimp 3.06 for Windows and tried to run gimp under wine., It starts, loads several plugins etc. but then crashes. And my plugin is not even installed yet. So no help there.

Since here are some people who know how to install a plugin under Windows I would like to ask you to install the plugin and send me the console output where some debug messages should appear.

To use the plugin do the following:
- open a file in Gimp 3.xx
- click File --> Export All (at the lower end of the menu) --> as PNG
- select an EMPTY folder to export to. Do not overwrite your existing files!
- untick the Export generated files only (otherwise the loaded file is skipped and is not written to disk)
- click OK

- on the export PNG window just click OK

The files then should appear in the specified folder.
Please send me the debug output on the console.
Thanks in advance.

CowboyJoe

[CowboyJoe]

I found the error.

Gitlab exports the zip file as
plugin-py-extract-all-main.
You have to rename the folder to
plugin-py3-extract-all. Then it is working.
I could not find a way on Gitlab to give it the proper name in the first place.

The problem does not occur when using git.

[rich2005]

Not working here: kubuntu 24.04 + gimp.org Gimp 3.2 RC1 appimage.  No files exported.  I did see some date  changes so a brand new download.

   

Attached the terminal output, which shows a few critical warnings.  Of course it might be an appimage thing.

[CowboyJoe]

Thank you for testing my plugin. 

In your errors.txt the log looks right.
My plugin starts with the "__init__()".
There are some warnings above this point that I am not sure if they are mine. They look like GUI-Errors, but my gui is loaded at a later point here:
Building GUI from file /home/rich/.config/GIMP/3.2/plug-ins/plugin-py3-export-all/./gui/SummaryWindow.glade

You loaded 3 files and exported them but since these files already have a representation on your disk(imported) they are skipped when you export them. When slicing images into pieces you do not want to export the original file, but the sliced pieces (generated) only.
To force the loaded files to export you have to untick the "Export generated files only". Then ALL files are exported, including loaded files. This is normally not desired so you have to untick it. The files should not end up in the skipped category then anymore. Just try to export them again with the Option unticked.

I noticed that the shadows in the summary window are heavily displaced. They have an offset of 3px. On low resolutions this could be too much. Maybe i replace that by some em-value.

Again: Thank you for your help.

[Ofnuts]

(11-26-2025, 11:32 PM)CowboyJoe Wrote: I found the error.

Gitlab exports the zip file as
plugin-py-extract-all-main.
You have to rename the folder to
plugin-py3-extract-all. Then it is working.
I could not find a way on Gitlab to give it the proper name in the first place.

The problem does not occur when using git.

It is a better idea to provide a .ZIP instead of relying on Gitlab. Everyone can unpack a ZIP, using Git is a developer skill. Also, the ZIP format will preserve the executable bit if set so your Linux/OSX users won't have to set it after unpacking.

[CowboyJoe]

(11-28-2025, 09:27 AM)Ofnuts Wrote: It is a better idea to provide a .ZIP instead of relying on Gitlab. Everyone can unpack a ZIP, using Git is a developer skill. Also, the ZIP format will preserve the executable bit if set so your Linux/OSX users won't have to set it after unpacking.

I tried to create a zipfile with gitlabs CI/CD but it failed. Why ? Not because I did something wrong, but because it needs verification by sms which is not working 99% of the time and does not tell the user why it failed. I got lucky once and managed to get the sms check done after a lot of trials. It is like a lottery. Now they want a credit card verification. This happens to people who they consider high risk users. Thank you, but no thank you. 
I will abandon this service and will move to some different one in the near future.

I tried with github and had no problems with the CI/CD so far. There are Gitea and OneDev still to test.

[Ofnuts]

Personally, I separate the source management (GitLab) from the distribution (SourceForge) and my CI/CD is mostly a small shell script to do the packaging.