Sign up now! · Forgot password?
RSS/Atom feed identi.ca Twitter

GIMP branched: new stable branch gimp-2-10

This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.

This is a read-only list on gimpusers.com so this discussion thread is read-only, too.

16 of 16 messages available
Toggle history

Please log in to manage your subscriptions.

GIMP branched: new stable branch gimp-2-10 Michael Natterer 20 May 19:17
  GIMP branched: new stable branch gimp-2-10 Carmelo DrRaw 20 May 19:27
   GIMP branched: new stable branch gimp-2-10 Michael Natterer 20 May 20:31
    GIMP branched: new stable branch gimp-2-10 Carmelo DrRaw 20 May 21:04
    GIMP branched: new stable branch gimp-2-10 Elle Stone 20 May 21:23
     GIMP branched: new stable branch gimp-2-10 Elle Stone 21 May 13:32
      GIMP branched: new stable branch gimp-2-10 Jehan Pagès 21 May 15:13
       GIMP branched: new stable branch gimp-2-10 Elle Stone 21 May 16:55
       GIMP branched: new stable branch gimp-2-10 Elle Stone 22 May 11:04
        GIMP branched: new stable branch gimp-2-10 Alexandre Prokoudine 22 May 11:18
        GIMP branched: new stable branch gimp-2-10 Simon Budig 22 May 11:33
         GIMP branched: new stable branch gimp-2-10 Jehan Pagès 22 May 14:01
          GIMP branched: new stable branch gimp-2-10 Kristian Rietveld 22 May 15:00
           GIMP branched: new stable branch gimp-2-10 Jehan Pagès 22 May 15:09
            GIMP branched: new stable branch gimp-2-10 Elle Stone 22 May 15:33
             GIMP branched: new stable branch gimp-2-10 Jehan Pagès 22 May 18:57
Michael Natterer
2018-05-20 19:17:01 UTC (29 days ago)

GIMP branched: new stable branch gimp-2-10

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

Enjoy! --Mitch

Carmelo DrRaw
2018-05-20 19:27:12 UTC (29 days ago)

GIMP branched: new stable branch gimp-2-10

What is the recommended branch for nightly development snapshots?

Should one provide snapshots for both master and gimp-2-10?

On 20 May 2018, at 21:17, Michael Natterer wrote:

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

Enjoy! --Mitch

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list

Michael Natterer
2018-05-20 20:31:30 UTC (29 days ago)

GIMP branched: new stable branch gimp-2-10

On Sun, 2018-05-20 at 21:27 +0200, Carmelo DrRaw wrote:

What is the recommended branch for nightly development snapshots?

Should one provide snapshots for both master and gimp-2-10?

That depends on what you want or what these snapshots are for:

gimp-2-10 is where 2.10.x releases are made from.

master is bleeding edge.

Regards, Mitch

On 20 May 2018, at 21:17, Michael Natterer wrote:

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

Enjoy! --Mitch

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-devel oper-list
List archives: https://mail.gnome.org/archives/gimp-developer-lis t

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-develop er-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

Carmelo DrRaw
2018-05-20 21:04:16 UTC (29 days ago)

GIMP branched: new stable branch gimp-2-10

On 20 May 2018, at 22:31, Michael Natterer wrote:

On Sun, 2018-05-20 at 21:27 +0200, Carmelo DrRaw wrote:

What is the recommended branch for nightly development snapshots?

Should one provide snapshots for both master and gimp-2-10?

That depends on what you want or what these snapshots are for:

In fact, it really depends on which kind of nightly snapshots you - the GIMP developers - would like to provide to users. I’m at your service ;-) If you would like to have the bleeding edge version tested also on OSX, I’m ready to provide the corresponding package… for the moment, I am restricting the packaging to the 2.10.x branch.

Andrea

gimp-2-10 is where 2.10.x releases are made from.

master is bleeding edge.

Regards, Mitch

On 20 May 2018, at 21:17, Michael Natterer wrote:

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

Enjoy! --Mitch

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-devel oper-list
List archives: https://mail.gnome.org/archives/gimp-developer-lis t

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-develop er-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list

Elle Stone
2018-05-20 21:23:06 UTC (29 days ago)

GIMP branched: new stable branch gimp-2-10

On 05/20/2018 04:31 PM, Michael Natterer wrote:

On Sun, 2018-05-20 at 21:27 +0200, Carmelo DrRaw wrote:

What is the recommended branch for nightly development snapshots?

Should one provide snapshots for both master and gimp-2-10?

That depends on what you want or what these snapshots are for:

gimp-2-10 is where 2.10.x releases are made from.

master is bleeding edge.

Hopefully related questions (otherwise my apologies for usurping the thread!):

I just installed gimp git master on Gentoo without any problems other than updating a couple of dependencies. It even runs :) .

git master 2.99/3.0 is where work on porting to GTK3 is happening - will anything else happen in git master for 3.0?

Specifically, will changes in handling of brushes and other painting assets (including high bit depth color palettes) be part of 2.10 or 3.0?

Is current git master more or less stable for actual use? For context, I started using GIMP-2.9 back in 2013 and from my point of view it was already sufficiently stable. I don't mind the occasional crash (well, assuming the crash doesn't destroy XCF files that aren't actually open for editing).

Best,
Elle

Regards,
Mitch

On 20 May 2018, at 21:17, Michael Natterer wrote:

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

Enjoy! --Mitch

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-devel oper-list
List archives: https://mail.gnome.org/archives/gimp-developer-lis t

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-develop er-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list

Elle Stone
https://ninedegreesbelow.com
Color management and free/libre photography
Elle Stone
2018-05-21 13:32:17 UTC (28 days ago)

GIMP branched: new stable branch gimp-2-10

Hi All,

On 05/20/2018 05:23 PM, Elle Stone wrote:

On 05/20/2018 04:31 PM, Michael Natterer wrote:

On Sun, 2018-05-20 at 21:27 +0200, Carmelo DrRaw wrote:

What is the recommended branch for nightly development snapshots?

Should one provide snapshots for both master and gimp-2-10?

That depends on what you want or what these snapshots are for:

gimp-2-10 is where 2.10.x releases are made from.

master is bleeding edge.

Is current git master more or less stable for actual use? For context, I started using GIMP-2.9 back in 2013 and from my point of view it was already sufficiently stable. I don't mind the occasional crash (well, assuming the crash doesn't destroy XCF files that aren't actually open for editing).

Regarding which branch to use for editing (as opposed to which branch(es) to provide for users to choose from), over on the gimp-gui mailing list Jehan had this to say about the new gimp git master branch, post-merging with the gtk+3 branch:

A note: are you actually planning on working with master? Even though for the last few years, master was absolutely production-usable, this is not the case with new master with GTK+3.

A lot of stuff is broken on the GTK+3 port. As I write this, I am working on the icon themes for instance which are completely broken. This is not production-ready. If you want a moving target while still stay usable, build "gimp-2-10" branch (which is old master). I predict it will still stay quite active, much more than what the "gimp-2-8" branch used to be since we will continue to backport features when possible/not too hard.

I had asked on the gimp-gui mailing list about some issues with the GTK+3/"new git" branch GTK+3 user interface. Even apart from other stuff that might be broken, the current git GIMP master GTK+3 interface is not very nice to use, at least not as it appears on my computer. The thread is here, if anyone is interested:

https://mail.gnome.org/archives/gimp-gui-list/2018-May/thread.html and click on the thread "gimp git master branch user interface".

Personally I've decided to hold off switching to the "new git/GTK+3" branch and stick with the 2.10 branch, at least until the user interface issues are resolved.

I guess changing toolkits is a necessary evil (eg QT4 to QT5, GTK+2 to GTK+3 with GTK+4 already in the wings . . . ). But it uses up a lot of developer time and energy, and the benefits of changing toolkits to the actual purposes for which we use editing software seem to me to be a bit iffy.

For a very insightful developer perspective on a comparable change in toolkits, when Krita went from QT4 to QT5, see this link:

https://valdyas.org/fading/software/krita-3-0/

Best, Elle

On 20 May 2018, at 21:17, Michael Natterer wrote:

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

Jehan Pagès
2018-05-21 15:13:05 UTC (28 days ago)

GIMP branched: new stable branch gimp-2-10

Hi!,

On Mon, May 21, 2018 at 3:32 PM, Elle Stone wrote:

Hi All,

On 05/20/2018 05:23 PM, Elle Stone wrote:

On 05/20/2018 04:31 PM, Michael Natterer wrote:

On Sun, 2018-05-20 at 21:27 +0200, Carmelo DrRaw wrote:

What is the recommended branch for nightly development snapshots?

Should one provide snapshots for both master and gimp-2-10?

That depends on what you want or what these snapshots are for:

gimp-2-10 is where 2.10.x releases are made from.

master is bleeding edge.

Is current git master more or less stable for actual use? For context, I

started using GIMP-2.9 back in 2013 and from my point of view it was already sufficiently stable. I don't mind the occasional crash (well, assuming the crash doesn't destroy XCF files that aren't actually open for editing).

Regarding which branch to use for editing (as opposed to which branch(es) to provide for users to choose from), over on the gimp-gui mailing list Jehan had this to say about the new gimp git master branch, post-merging with the gtk+3 branch:

A note: are you actually planning on working with master? Even though

for the last few years, master was absolutely production-usable, this is not the case with new master with GTK+3.

A lot of stuff is broken on the GTK+3 port. As I write this, I am working on the icon themes for instance which are completely broken. This is not production-ready. If you want a moving target while still stay usable, build "gimp-2-10" branch (which is old master). I predict it will still stay quite active, much more than what the "gimp-2-8" branch used to be since we will continue to backport features when possible/not too hard.

I had asked on the gimp-gui mailing list about some issues with the GTK+3/"new git" branch GTK+3 user interface. Even apart from other stuff that might be broken, the current git GIMP master GTK+3 interface is not very nice to use, at least not as it appears on my computer. The thread is here, if anyone is interested:

https://mail.gnome.org/archives/gimp-gui-list/2018-May/thread.html and click on the thread "gimp git master branch user interface".

Personally I've decided to hold off switching to the "new git/GTK+3" branch and stick with the 2.10 branch, at least until the user interface issues are resolved.

I guess changing toolkits is a necessary evil (eg QT4 to QT5, GTK+2 to GTK+3 with GTK+4 already in the wings . . . ). But it uses up a lot of developer time and energy, and the benefits of changing toolkits to the actual purposes for which we use editing software seem to me to be a bit iffy.

Just to be clear, the toolkit update here is not *just* a necessary evil. It will also be totally awesome, even feature-wise! Without doing much, the differences are already dramatically awesome IMO, like the simple fact that input devices (read: graphics tablet) don't have to be activated manually, nor plugged before running GIMP (hotplug support), etc. Then we'll be able to add touch support (zoom, pan, rotation of canvas with fingers).
And much more. This is very exciting. In any case, the benefits are definitely not "iffy".

Simply to get there, we have to pass through an "unstable" phase, that's all there is to it. The old master (which became 2.10) has had this phase too, I can definitely tell so. When I started contributed, back in 2012, it was absolutely unusable for daily use as well (though you say you were already using the master build daily back in 2013, but maybe you are less demanding as us :P). Not only unstable, but also slow as hell. Absolutely impossible to use for painting.
This is just how software development works. :-)

Jehan

For a very insightful developer perspective on a comparable change in toolkits, when Krita went from QT4 to QT5, see this link:

https://valdyas.org/fading/software/krita-3-0/

Best, Elle

On 20 May 2018, at 21:17, Michael Natterer wrote:

Hi everybody,

We just branched:

Stable GIMP 2.10.x lives on the new gimp-2-10 branch now.

The gtk3-port branch has been merged to master, we're back to normal development in master again.

_______________________________________________

gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman /listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
Elle Stone
2018-05-21 16:55:35 UTC (28 days ago)

GIMP branched: new stable branch gimp-2-10

On 05/21/2018 11:13 AM, Jehan Pagès wrote:

Hi!,

Hi Jehan and all,

On Mon, May 21, 2018 at 3:32 PM, Elle Stone

I guess changing toolkits is a necessary evil (eg QT4 to QT5, GTK+2 to GTK+3 with GTK+4 already in the wings . . . ). But it uses up a lot of developer time and energy, and the benefits of changing toolkits to the actual purposes for which we use editing software seem to me to be a bit iffy.

Just to be clear, the toolkit update here is not *just* a necessary evil. It will also be totally awesome, even feature-wise! Without doing much, the differences are already dramatically awesome IMO, like the simple fact that input devices (read: graphics tablet) don't have to be activated manually, nor plugged before running GIMP (hotplug support), etc. Then we'll be able to add touch support (zoom, pan, rotation of canvas with fingers).
And much more. This is very exciting. In any case, the benefits are definitely not "iffy".

Good to know!

Simply to get there, we have to pass through an "unstable" phase, that's all there is to it. The old master (which became 2.10) has had this phase too, I can definitely tell so. When I started contributed, back in 2012, it was absolutely unusable for daily use as well (though you say you were already using the master build daily back in 2013, but maybe you are less demanding as us :P). Not only unstable, but also slow as hell. Absolutely impossible to use for painting.

Back in 2012/2013 I was editing photographs. So the speed of painting only affected painting on a layer mask, which indeed was slooooow.

For photographic editing GIMP-2.9 was already useable even in middle-late 2012, at least it was after I somehow managed ("somehow" meaning with a *great* deal of help from various GIMP devs) to port the old LCMS plug-in from LCMS1 to LCMS2, which is when and why I started contributing to GIMP development:

http://gimp.1065349.n5.nabble.com/no-subject-td28716.html http://gimp.1065349.n5.nabble.com/the-Gimp-lcms-c-plug-in-td34453i20.html

My February 2013 review of The Book of GIMP (https://ninedegreesbelow.com/photography/book-of-gimp.html) has a sample image processed using GIMP-2.9: https://ninedegreesbelow.com/photography/gimp/bog/rapidly-departing-storm-clouds.jpg - the image was processing using GIMP-2.9's ability to add +4 stops of exposure compensation to a copy of a layer to lighten the ground, and then "paint" the now out-of-gamut sky areas back in to the desired degree of exposure - at the time and maybe even now, as far as I know no other image editor makes this sort of editing possible.

Best, Elle

Elle Stone
2018-05-22 11:04:08 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

On 05/21/2018 11:13 AM, Jehan Pagès wrote:

Just to be clear, the toolkit update here is not*just* a necessary evil. It will also be totally awesome, even feature-wise!

Simply to get there, we have to pass through an "unstable" phase, that's all there is to it.

Hi All,

Apparently GTK+3.22 is considered "long term stable" (that is, supported for three years? starting from when?) and is the last minor release in the GTK+3 series:
https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-promise-in-gtk/

Will the port to GTK+3 be finished before the apparently planned initial release of GTK+4 later this year
(https://blogs.gnome.org/mclasen/2018/02/03/gtk-hackfests-day-2/)?

Will the port from GTK+3 to GTK+4 be as difficult as the port from GTK+2 to GTK+3? Looking at various NEWS postings in the 3.93/.92/etc releases leading up to GTK+4 (http://ftp.acc.umu.se/pub/gnome/sources/gtk+/), it looks like a fair amount of stuff will change.

Best, Elle

Alexandre Prokoudine
2018-05-22 11:18:47 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

On Tue, May 22, 2018 at 2:04 PM, Elle Stone wrote:

Will the port to GTK+3 be finished before the apparently planned initial release of GTK+4 later this year
(https://blogs.gnome.org/mclasen/2018/02/03/gtk-hackfests-day-2/)?

How can one possibly provide a realistic estimation of that? :)

Alex

Simon Budig
2018-05-22 11:33:11 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

Elle Stone (ellestone@ninedegreesbelow.com) wrote:

On 05/21/2018 11:13 AM, Jehan Pagès wrote:

Just to be clear, the toolkit update here is not*just* a necessary evil. It will also be totally awesome, even feature-wise!

Simply to get there, we have to pass through an "unstable" phase, that's all there is to it.

Apparently GTK+3.22 is considered "long term stable" (that is, supported for three years? starting from when?) and is the last minor release in the GTK+3 series: https://blog.gtk.org/2016/09/01/versioning-and-long-term-stability-promise-in-gtk/

Just to clarify, the "unstable" phase happens because we're migrating the toolkit, not because the toolkit we're migrating to is unstable...

Will the port from GTK+3 to GTK+4 be as difficult as the port from GTK+2 to GTK+3? Looking at various NEWS postings in the 3.93/.92/etc releases leading up to GTK+4 (http://ftp.acc.umu.se/pub/gnome/sources/gtk+/), it looks like a fair amount of stuff will change.

I guess we'll see. The major concern I have is related to our own ABI compatibility. Is there a way to decouple our ABI version from the GTK version? This is what forced us to stick with gtk2 for that long timeframe, and that sucked...

Bye, Simon

simon@budig.de              http://simon.budig.de/
Jehan Pagès
2018-05-22 14:01:47 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

Hi!

On Tue, May 22, 2018 at 1:33 PM, Simon Budig wrote:

Elle Stone (ellestone@ninedegreesbelow.com) wrote:

On 05/21/2018 11:13 AM, Jehan Pagès wrote:

Just to be clear, the toolkit update here is not*just* a necessary

evil.

It will also be totally awesome, even feature-wise!

Simply to get there, we have to pass through an "unstable" phase,

that's

all there is to it.

Apparently GTK+3.22 is considered "long term stable" (that is, supported

for

three years? starting from when?) and is the last minor release in the

GTK+3

series: https://blog.gtk.org/2016/09/01/versioning-and-long-term-

stability-promise-in-gtk/

Just to clarify, the "unstable" phase happens because we're migrating the toolkit, not because the toolkit we're migrating to is unstable...

Will the port from GTK+3 to GTK+4 be as difficult as the port from GTK+2

to

GTK+3? Looking at various NEWS postings in the 3.93/.92/etc releases

leading

up to GTK+4 (http://ftp.acc.umu.se/pub/gnome/sources/gtk+/), it looks

like a

fair amount of stuff will change.

I guess we'll see.

There is another issue which was raised these days by GTK+ developers who discussed GIMP port: apparently GTK+3.99 (to become GTK+4) has currently no macOS backend! Basically that means we'd lose GIMP on macOS. And worse, they have (nearly or none at all?) no developers working on this, so it's not even sure when or if it will come.

Actually even GTK+3 macOS port is bad but at least there is something. The Windows backend on GTK+3 is bad too (still according to GTK+ devs) but is more tested than Windows backend.

So yeah thinking about porting to GTK+4 is far too early. And anyway we have already far enough to do. Deciding to port to a moving target (i.e. unstable API) would be just masochistic.

The major concern I have is related to our own ABI compatibility. Is there a way to decouple our ABI version from the GTK version? This is what forced us to stick with gtk2 for that long timeframe, and that sucked...

I think that is definitely a good point, and I am in favor of creating as much high level "semantic" API as possible (when it makes sense). This would create some boiler plate intermediate code, but is definitely worth it on the long run IMO.

Jehan

Bye,
Simon

--
simon@budig.de http://simon.budig.de/ _______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp- developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
Kristian Rietveld
2018-05-22 15:00:16 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

On 22 May 2018, at 16:01, Jehan Pagès wrote:

There is another issue which was raised these days by GTK+ developers who discussed GIMP port: apparently GTK+3.99 (to become GTK+4) has currently no macOS backend! Basically that means we'd lose GIMP on macOS. And worse, they have (nearly or none at all?) no developers working on this, so it's not even sure when or if it will come.

The macOS backend been fully removed in 3.99??

Actually even GTK+3 macOS port is bad but at least there is something. The Windows backend on GTK+3 is bad too (still according to GTK+ devs) but is more tested than Windows backend.

I worked on the GTK+3 macOS port in the early beginning of GTK+3. I don’t know how much work went into it after that, I did get the impression that it got commits and maintenance regularly.

I wasn’t really looking forward to the GTK+3 port because of this and the fact that the entire backend appears to have been removed doesn’t really make it better :( On the other hand, it should probably be much easier to port GTK+3/4 to macOS compared to GTK+2.

regards,

-kris.

Jehan Pagès
2018-05-22 15:09:49 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

Hi!

On Tue, May 22, 2018 at 5:00 PM, Kristian Rietveld wrote:

On 22 May 2018, at 16:01, Jehan Pagès

wrote:

There is another issue which was raised these days by GTK+ developers who discussed GIMP port: apparently GTK+3.99 (to become GTK+4) has currently

no

macOS backend! Basically that means we'd lose GIMP on macOS. And worse, they have (nearly or none at all?) no developers working on this, so it's not even sure when or if it will come.

The macOS backend been fully removed in 3.99??

I have no idea. Has it been removed? Is it still here but just completely broken and waiting to be fixed?
Or simply so untested that none really knows?

For information, I am referring to this discussion: https://twitter.com/acruiz/status/998552715654463489 As you can see, the first message is:

Gtk4 doesn't have a Mac backend AFAIK and I'm not sure it's widely tested

on Windows
(by Alberto Ruiz)

Actually even GTK+3 macOS port is bad but at least there is something.

The

Windows backend on GTK+3 is bad too (still according to GTK+ devs) but is more tested than Windows backend.

I worked on the GTK+3 macOS port in the early beginning of GTK+3. I don’t know how much work went into it after that, I did get the impression that it got commits and maintenance regularly.

I wasn’t really looking forward to the GTK+3 port because of this and the fact that the entire backend appears to have been removed doesn’t really make it better :( On the other hand, it should probably be much easier to port GTK+3/4 to macOS compared to GTK+2.

Don't take my word for it. I was just relaying what I understood from the Twitter thread above, which may itself not be perfectly informed. It seems clear that the macOS backend is not that maintained though, seeing how various GTK+ devs are clearly stating this as a fact, but I actually guess they would not just remove years of code just on a whim (I hope so).

Jehan

regards,

-kris.

ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot
Elle Stone
2018-05-22 15:33:48 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

On 05/22/2018 11:09 AM, Jehan Pagès wrote:

Gtk4 doesn't have a Mac backend AFAIK and I'm not sure it's widely tested

on Windows

Hmm, this page seems to indicate GTK+4 does/will have support for MacOs: https://www.phoronix.com/scan.php?page=news_item&px=GTK-3.91-Released

quoting: "GTK+ 3.91 brings initial Meson build system support, GTK4 native support for macOS, and nearly two dozen bug fixes."

Best, Elle

Jehan Pagès
2018-05-22 18:57:38 UTC (27 days ago)

GIMP branched: new stable branch gimp-2-10

On Tue, May 22, 2018 at 5:33 PM, Elle Stone wrote:

On 05/22/2018 11:09 AM, Jehan Pagès wrote:

Gtk4 doesn't have a Mac backend AFAIK and I'm not sure it's widely tested

on Windows

Hmm, this page seems to indicate GTK+4 does/will have support for MacOs: https://www.phoronix.com/scan.php?page=news_item&px=GTK-3.91-Released

quoting: "GTK+ 3.91 brings initial Meson build system support, GTK4 native support for macOS, and nearly two dozen bug fixes."

Maybe. As I said, I was only extrapolating from a single discussion on some "social network".
In any case, the macOS backend may be there, but in a poor state apparently, since I believe that a discussion between several contributors of GTK+ (one of them being still a very regular contributor, and another being the maintainer!) is definitely more trustworthy than whatever press. :-)

Yet once again, do not take my word for it.

Jehan

Best,
Elle

_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman /listinfo/gimp-developer-list
List archives: https://mail.gnome.org/archives/gimp-developer-list

ZeMarmot open animation film
http://film.zemarmot.net
Liberapay: https://liberapay.com/ZeMarmot/
Patreon: https://patreon.com/zemarmot
Tipeee: https://www.tipeee.com/zemarmot