I’d like it to stay under ~/.config, I don’t like my home directory littered with too much stuff.
Yes, I agree. What I am proposing is to use a different folder under ~/.config, or actually under $XDG_CONFIG_HOME.
Ah, in that case I like GIMP-appimage
I Think it would be great if it were independent from the 2.8 installation (or any git one you may have).
This is running well on Fedora 24. The ORF file opens directly in PhotoFlow for me.
~./config/config is a bit weird but does not really matter providing the user knows where to find your Gimp 2.9 profile. Easy enough if you look in Edit → Preferences → Folders
On an old laptop using Kubuntu and gimp-edge ppa installation, the 2.9 profile is ~/.config/GIMP so for consistency that is favourite.
However, this machine, also Kubuntu I already have a Gimp 2.9.3 appimage from
https://bintray.com/probono/AppImages/ with a profile ~/.config/GIMP so from my point of view a separate ~/.config/GIMP-appimage prevents conflicts.
End of the day, does not really matter, when you get tired of delving into say, ~/.config/config/2.9/plug-ins/ to install a plugin, set up a folder in your home partition and add that as a plugin folder.
I have prepared a new version of the GIMP+gmic+PhF appimage package, which can be found here: Dropbox - gimp-2.9.5.glibc2.15-x86_64-20160807.AppImage - Simplify your life
The main improvements with respect to the first version are the following:
- the gimp configuration directory is now set to ~/.config/GIMP-AppImage
- some bugs on the photoflow side have been fixed
- photoflow is now always used for RAW processing. At some point, Gimp will hopefully have a mechanism to choose the preferred RAW loading plug-in, for example an interface to enable/disable individual plug-ins…
- the G’MIC film emulation LUTs are now included by default in the AppImage, and can be used out-of-the-box
Feedback appreciated as usual!
I’ve tested the previous version with no issues: I have 2.8 ane a 2.9.5 git version and everything has worked fine. I had problems not seeing the bottom part of the window with 2.9.5 git, but it works just fine with your appimage.
Just one thing ¿does anyone know how could I make work the Heal Selection plugin?
I will gladly get you access to the server here to host any files you need.
Love the work your doing, thank you!
I’ll be glad to accept the offer! Probably the current version is already good enough for a wider audience…
You need the appropriate resynthesizer and resynthesizer-gui plugins for your version of linux as well as the plugin-heal-selection.py If you have them already in your Gimp 2.8 installation use those.
Same as any plugins, they go in the Gimp profile, in this case ~/.config/GIMP-appimage/plug-ins
Get to expect deprecated function error messages. In this case the heal-selection plugin still works but needs updating.
A quick try running this appimage with the switch –pdb-compat-mode=on does not make any difference. Such is life.
Running from a terminal I see this gmic error.
GIMP-Error: Unable to run plug-in “gmic_film_cluts.gmz”
Not a plugin & not marked as executable so I do not know why it tries to run?
However I do not think that should be in the root plug-ins folder. These days gmic has its own folder in ~/.config/gmic
AFAIK the appimage will use that one.
It helped, also with another problem on a diffrent pc.
Pardon my ignorance, but how do I uninstall the previous appimage to replace it with the latest one above?
Just delete the current AppImage from where ever you put that file, then download the new one, do a
chmod a+x file.appimage, then launch it.
AppImages don’t really get “installed,” you just download and execute the file.
This can be a convenient way to test different versions of a given program.b
That would however leave the
.desktop file behind.
I am not sure that this will work with the AppImage, because the resynthesizer plug-ins are in this case compiled for a different GIMP version, and therefore there will be very likely some binary incompatibilities.
Moreover, in my view this appimage package should be considered as an all-in-one solution for digital photography & painting, especially targeted to new users who do not want to spend half a day installing useful optional stuff. So all plug-ins which are relevant should be already bundled in the appimage, and directly available without extra efforts.
I will add the resynthesizer and plugin-heal-selection.py to the bundle. If you have other suggestions for useful plug-ins, just let me know…
I think I will simply disable the installation of the .desktop file, because I find it a bit confusing… starting the appimage from the file browser should be much more familiar for people coming from the dark side of the desktop world
Putting plugins in the appimage Gimp profile works fine here: Kubuntu 16.04
We are coming from completely different viewpoints here. I think a plugin should be in the appimage gimp profile where it can be easily changed. If it is incorporated in the appimage, any update means the user downloads the complete appimage again. Think appimage = 130MB to update gmic_gimp = 7 MB and gmic updates almost every week.
edit: although I have a feeling that the plugin in the gimp profile will take precedence so maybe not such a problem
A prime example is the Debian package gimp-plugin-repository dozens of scripts/plugins most of which never used, all buried in the root directories never to be (easily) found.
Not needed for me, but the resynthesizer plugin is worth including. As a suggestion liquid-rescale.
If you add the heal-selection.py plug-in, line 75 generates a deprecated function warning, should be
pdb.gimp_image_select_item(tempImage, 1, orgSelection)
Anyway a great tool for getting to grips with Gimp 2.9 and still keeping Gimp 2.8 I am a great fan of portable applications, not all have to be bundled as an single file, but it helps.
Much appreciate all the effort.