Re: [Gimp-developer] GIMP branched: new stable branch gimp-2-10
- From: Simon Budig <simon budig de>
- To: gimp-developer-list gnome org
- Subject: Re: [Gimp-developer] GIMP branched: new stable branch gimp-2-10
- Date: Tue, 22 May 2018 13:33:11 +0200
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!
<snip>
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/
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]