Re: [Gimp-developer] How to retrieve the monitor profile from inside a plug-in

I was thinking for my own purposes, but it might be a useful way to let
people test different configurations without having to change the defaults
they are used to. That's one thing I love about the AppImage, is it can
happily live right along side my installed ppa, and I have two versions of
GIMP, one that lets me assist others, and another tweaked to my preferences.

Also, remember how popular GIMPshop was for a while? It was mainly just a
ver of GIMP with re-mapped hotkeys.
I still hear people asking for it, and since that project is dead, it has
become a bit of a hazard...

A better option would be to have an AppImage with remapped hotkeys. I mean,
it's still not good, but better than people trying to install untrustworthy
tarballs with adware.

In the near future, I want to set up a website dedicated to sharing and
revising workflows in GIMP and other FLOSS programs.
I'd like to make a game of seeing how fast things can be done for various
workflows and revise mine, and share. It will be easier to identify
workflow bottlenecks, so the ones that are common between different tasks
can be addressed, plans drawn up, and submitted along with workflow
statistics to GIMP devs for consideration. I believe this would be much
more useful than simply complaining that one thing affects one workflow,
and offering half, or bad solutions to the problem.

It would be neat to let people try out new configs based on the
current-fastest setup without moving a lot of files around, and leaves devs
free to attend to more important things than hotkey preferences.

Thanks again for the info. :)

On Thu, Sep 8, 2016 at 8:43 AM, Carmelo DrRaw <aferrero1975 gmail com>

On 08 Sep 2016, at 09:01, C R <cajhne gmail com> wrote:

Indeed. I'm finding the speed to be roughly the same as I'm used to with
the GIMP ppa.

Out of curiosity, is it possible to package a different set of GIMP
defaults with an AppImage?
For example, say I wanted to:

1. Set NoHalo as the default interpolation mode for all transformations
2. Set the preview opacity to 75% during all transformations
3. Map (or remap) hotkeys

Is there a way to do this in an AppImage?

There might be a way to do that, but I would be very reluctant to do so,
simply because each person has its own preferences…

But you can easily copy your GIMP preferences over to the appimage, like

cp -a $HOME/.config/GIMP/2.9 $HOME/.config/GIMP-AppImage/
rm -f $HOME/.config/GIMP-AppImage/pluginrc




On Wed, Sep 7, 2016 at 9:33 PM, Carmelo DrRaw <aferrero1975 gmail com>

On 07 Sep 2016, at 22:28, C R <cajhne gmail com> wrote:

This is fantastic! I could see this become my preferred way to use GIMP.
G'MIC works like a charm, can't make it break. Used a 2000x2000 test
image, and it just flies!

At this point, the performances of the AppImage should be very close, if
not equivalent, to the standard GIMP.

Well done, and thanks!

You are welcome!


On Tue, Sep 6, 2016 at 7:13 PM, Carmelo DrRaw <aferrero1975 gmail com>

Thanks, it worked!!!

The only part which is still missing is the tracking of monitor changes.

I have prepared a special GIMP AppImage with the patched gmic plug-in,
if anyone is interested to test it and give some feedback:


On 06 Sep 2016, at 18:35, Michael Natterer <mitch gimp org> wrote:

On Tue, 2016-09-06 at 16:47 +0200, Carmelo DrRaw wrote:

On 06 Sep 2016, at 16:41, Michael Natterer <mitch gimp org> wrote:

On Tue, 2016-09-06 at 16:30 +0200, Carmelo DrRaw wrote:

In GIMP git master, you would say

gimp_preview_area_set_color_config (gimp_preview_get_area

Thanks! However, I assume that the ICC conversion is done in this
case using 8-bits precision, right?

I would like to take advantage of the fact that G’MIC handles
floating-point precision, by doing the ICC conversion before the
conversion to 8-bits…

Moreover, this API only makes sure an assumed-to-be-sRGB image
is displayed correctly in 8 bit.

You can omit this call, and feed color-corrected pixels to
the preview directly, look at the GimpColorTransform API
in libgimpcolor, which is a simple wrapper around lcms
(which you don't need to use at all).

For the image profile, use gimp_image_get_effective_color_profile(),

for getting the transform, best use gimp_widget_get_color_transform()
which will look up the right display profile by itself.

Also, use gimp_widget_track_monitor() so you can recreate
the transform when the window is moved to another monitor.

For example code, grep for


in libgimpwidgets/ and app/widgets/


My question was if this is a plug-in against GIMP 2.8 (soon
or against GIMP git master.

I wouldn't bother do add color management to a GIMP 2.8 plug-in
and I have never tried.

I see… G’MIC is already adapted to high bit depth and 2.9 API, so I
think it is worth adding proper color management.


gimp-developer-list mailing list
List address:    gimp-developer-list gnome org <mailto:
gimp-developer-list gnome org>
List membership:
List archives:
gimp-developer-list mailing list
List address:    gimp-developer-list gnome org
List membership:
List archives:

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]