doobs
(Christopher J Dubea)
September 13, 2024, 10:35pm
1
So,
After a LOT of blustering earlier in the year about the imminent arrival of v3.0, there had been a complete vacuum of information about the subject.
I’m taking the lack of information to be a sign that all is not well in Mudville.
Does anyone here have any info that they would be willing to share?
I mean we’ve been waiting for v3.0 for what, 10 years? And then after all this time to seemingly have the right pulled out from under us?
Please throw a dog a bone guys…
Sorry for the stupid title, but website rules of 15 characters
How could there be a rug pull when all the development is done in the open?
https://developer.gimp.org/core/roadmap/#gimp-30-development-branch-roadmap
2 Likes
veles
(veles worth)
September 15, 2024, 4:50pm
3
I can’t use GMIC for 2.99.19.1 RC3.0.
Since GMIC is a plugin, this isn’t that surprising. I’m sure once 3.0 is finalized that it’ll work.
veles
(veles worth)
September 15, 2024, 7:35pm
5
Only 5% of things sorted out till 3.0.
1 Like
Hello everyone,
GIMP 3.0, as soon as it is released, will be able to work with G’MIC.
https://x.com/gmic_eu/status/1830672897242787989
GIMP 3.0 is now on string feature freeze in preparation for the “upcoming” release.
If you take a look at its commits, at present, it is indeed mostly only bug-fixing work:
6 Likes
darix
(darix)
September 15, 2024, 8:27pm
7
it is of course all your fault because you are not helping with finishing it.
Just saying.
mikae1
September 16, 2024, 5:10am
8
Considering the list of things left to do in
I’m sure @doobs will have his stable 3.0 release by at least 2034. I note that Wayland color management is the list.
If you really want features now @doobs , you could try this .
GIMP is in string freeze for 3.0, so it’s almost done.
What will everyone complain about after it comes out? I’m sure y’all will find something.
1 Like
mikae1
September 16, 2024, 5:48am
10
Actually, it was not a complaint. I’m not in a hurry. Those in a hurry could use GIMP 3 in it’s current, unfinished, form.
The roadmap gives the impression that there’s more working remaining than there actually is.
For instance, Redesign API is almost done - we have merge requests to solve the last two items on it. Likewise with the color space invasion and improved Wayland support.
A better indicator to track is the 3.0 RC1 milestones , which are currently around 95% done with 15 issues remaining. We had some unexpected delays earlier due to developers getting sick and the like, but things have really picked up in the last month or so.
8 Likes
doobs
(Christopher J Dubea)
September 16, 2024, 2:14pm
12
Dunno what almost means…
I’m 67 years old. I’m hoping to see v3.0 whilst I’m amongst the living.
doobs:
Dunno what almost means
The point is that you can find out for yourself. Or you can ask in a way that isn’t obnoxiously entitled.
doobs
(Christopher J Dubea)
September 16, 2024, 3:11pm
14
Well,
Based upon this answer, almost means absolutely nothing. Could be a day, could be a decade. All it really means is go away, don’t bother me.
I’m pretty much done with you and your holier than thou attitude.
Cheers mate…
mikae1
September 16, 2024, 3:31pm
15
cmyk.student:
The roadmap gives the impression that there’s more working remaining than there actually is.
For instance, Redesign API is almost done - we have merge requests to solve the last two items on it. Likewise with the color space invasion and improved Wayland support.
A better indicator to track is the 3.0 RC1 milestones , which are currently around 95% done with 15 issues remaining. We had some unexpected delays earlier due to developers getting sick and the like, but things have really picked up in the last month or so.
Thanks for reporting! Happy to see that you’re getting closer.
doobs:
Based upon this answer, almost means absolutely nothing. Could be a day, could be a decade. All it really means is go away, don’t bother me. I’m pretty much done with you and your holier than thou attitude. Cheers mate…
You actually shouldn’t bother people devoting their spare time to giving you something for free. This is not Photoshop. You haven’t payed. They develop, but they do it on their terms. Be nice. Stay constructive.
4 Likes
darix
(darix)
September 16, 2024, 3:35pm
16
While waiting you could watch the following video
It might help you understand why your attitude is maybe inappropriate.
1 Like
veles
(veles worth)
September 16, 2024, 6:40pm
17
What does it need to change in GTK4/5 to have faster and easier development of GIMP 4?
Because API was quite old and my outsider impression it has a lot of heavy lift.
What does it need to change in GTK4/5 to have faster and easier development of GIMP 4?
Quite simply, much more full-time developers working on it
Joking aside, moving from GTK3 to GTK4 is not that simple and requires quite a lot of work. For instance, to make it working on many platforms (Windows, Mac) and not only Linux (which is where GTK4 is mostly tested).
At present, to my knowldege (on top of GIMP), there are no big important open source (e.g. darkable, RawTherapee, LibreOffice) softwares based on GTK (as GUIs) which run GKTK4 , as their toolkit.
From what I have read, Inkscape hired a full-time developer to port the software from GTK3 to GTK4. Currently, this work has been mostly done but there are many regressions (especially on Windows and Mac) which will require quite more efforts.
Perhaps, who knows, Inkscape 1.5 will run on GTK4.
It suffices to take a look at what needs to be done for darktable to understand the magnitude of this very daunting task:
opened 07:33AM - 21 Dec 23 UTC
no-issue-activity
gtk4
Hello to everyone,
just to document the state of migration, if anyone wants t… o help. For now, I will just use the migration documentation on https://docs.gtk.org/gtk4/migrating-3to4.html as a todo list. Just because that is, how I will handle it. So everyone can see how far I am/we are. The list might be incomplete and filled with time. Feel free to edit it with care.
Also, feel free to reopen tasks, if you think they are not solved cause of whatever reason. If for one point exist one or more pr that include the whole work, close the point here with reference to the pr(s). It would be awesome if anyone writes a note to a task she/he is working on. I would suggest to take care of every point, also if one point might be obviously checked. It is just that we have everything in mind.
At the point of starting with the hard migration, it might be helpful to have an separate branch for it centrally and not in everyone fork repo.
If this issue will be accepted for documentation, #13236 might be closed with reference to this entry.
Last point: This is just a suggestion how this work might be done and tracked.
Edit: 02.06.2024 - No inactivity.
## Preparation in GTK 3.x
- [x] **Do not use deprecated symbols** Checked it and couldn't find any deprecated symbols. Please anyone verify! (Feels a little bit uncertain that no dep symbol is in use. Maybe I just did something wrong.)
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [x] **Enable diagnostic warnings**
#15898
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [ ] **Do not use GTK-specific command line arguments**
Couldn't find any use of it, but I am not sure.
- [ ] **Do not use widget style properties**
In code I only found vertical-separator in gtk.c on line 3238. I don't know how to get this value without properties in gtk3. The effect is not big if it will be removed. Mostly the scrolling is not exactly one row.
- [x] **Review your window creation flags** Couldn't find any.
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [ ] **Stop using direct access to GdkEvent structs**
- [x] **Stop using gdk_pointer_warp()** Couldn't find any.
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [ ] **Stop using non-RGBA visuals**
- [x] **Stop using gtk_widget_set_app_paintable**
#15908
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [x] **Stop using GtkBox padding, fill and expand child properties** Couldn't find any.
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [x] **Stop using the state argument of GtkStyleContext getters** Couldn't find any.
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [x] **Stop using gdk_pixbuf_get_from_window() and gdk_cairo_set_source_window()** Couldn't find any.
(Done-by: @Christian-Kr; Date: 21.12.2023)
- [ ] **Stop using GtkButton's image-related API**
- [ ] **Stop using GtkWidget event signals**
#15923
#16919
(Progress-by: @Christian-Kr; Date: 21.12.2023)
- [ ] **Set proper application ID**
- [ ] **Stop using gtk_main() and related APIs**
- [ ] **Reduce the use of gtk_widget_destroy()**
- [ ] **Stop using the GtkWidget.destroy vfunc**
- [ ] **Reduce the use of generic container APIs**
- [ ] **Review your use of icon resources**
## Changes that need to be done at the time of the switch
- [ ] **Subclassing**
- [ ] **Life-cycle handling**
- [ ] **Stop using GdkScreen**
- [ ] **Stop using the root window**
- [ ] **Stop using GdkVisual**
- [ ] **Stop using GdkDeviceManager**
- [ ] **Adapt to GdkWindow API changes**
- [ ] **The "Iconified" window state has been renamed to "minimized"**
- [ ] **Adapt to GdkEvent API changes**
- [ ] **Stop using grabs**
- [ ] **Adapt to coordinate API changes**
- [ ] **Adapt to GdkKeymap API changes**
- [ ] **Adapt to changes in keyboard modifier handling**
- [ ] **Replace GtkClipboard with GdkClipboard**
- [ ] **Stop using gtk_get_current_... APIs**
- [ ] **Convert your UI files**
- [ ] **Adapt to GtkBuilder API changes**
- [ ] **Adapt to event controller API changes**
- [ ] **Focus handling changes**
- [ ] **Use the new apis for keyboard shortcuts**
- [ ] **Stop using GtkEventBox**
- [ ] **Stop using GtkButtonBox**
- [ ] **Adapt to GtkBox API changes**
- [ ] **Adapt to GtkWindow API changes**
- [ ] **Adapt to GtkHeaderBar and GtkActionBar API changes**
- [ ] **Adapt to GtkStack, GtkAssistant and GtkNotebook API changes**
- [ ] **Adapt to GtkScrolledWindow API changes**
- [ ] **Adapt to GtkBin removal**
- [ ] **Adapt to GtkContainer removal**
- [ ] **Stop using GtkContainer::border-width**
- [ ] **Adapt to gtk_widget_destroy() removal**
- [ ] **Adapt to coordinate API changes**
- [ ] **Adapt to GtkStyleContext API changes**
- [ ] **Adapt to GtkCssProvider API changes**
- [ ] **Stop using GtkShadowType and GtkRelief properties**
- [ ] **Adapt to GtkWidget's size request changes**
- [ ] **Adapt to GtkWidget's size allocation changes**
- [ ] **Switch to GtkWidget's children APIs**
- [ ] **Don't use -gtk-gradient in your CSS**
- [ ] **Don't use -gtk-icon-effect in your CSS**
- [ ] **Don't use -gtk-icon-theme in your CSS**
- [ ] **Don't use -gtk-outline-...-radius in your CSS**
- [ ] **Adapt to drawing model changes**
- [ ] **Stop using APIs to query GdkSurfaces**
- [ ] **Widgets are now visible by default**
- [ ] **Adapt to changes in animated hiding and showing of widgets**
- [ ] **Stop passing commandline arguments to gtk_init**
- [ ] **GdkPixbuf is deemphasized**
- [ ] **GtkWidget event signals are removed**
- [ ] **Invalidation handling has changed**
- [ ] **Stop using GtkWidget::draw**
- [ ] **Window content observation has changed**
- [ ] **Monitor handling has changed**
- [ ] **Adapt to monitor API changes**
- [ ] **Adapt to cursor API changes**
- [ ] **Adapt to icon size API changes**
- [ ] **Adapt to changes in the GtkAssistant API**
- [ ] **Adapt to changes in the API of GtkEntry, GtkSearchEntry and GtkSpinButton**
- [ ] **Adapt to changes in GtkOverlay API**
- [ ] **Use GtkFixed instead of GtkLayout**
- [ ] **Adapt to search entry changes**
- [ ] **Adapt to GtkScale changes**
- [ ] **Stop using gtk_window_active_default()**
- [ ] **Stop using gtk_widget_grab_default()**
- [ ] **Stop setting ::has-default and ::has-focus in .ui files**
- [ ] **Stop using the GtkWidget::display-changed signal**
- [ ] **GtkPopover::modal has been renamed to autohide**
- [ ] **gtk_widget_get_surface has been removed**
- [ ] **gtk_widget_is_toplevel has been removed**
- [ ] **gtk_widget_get_toplevel has been removed**
- [ ] **GtkEntryBuffer ::deleted-text has changed**
- [ ] **GtkMenu, GtkMenuBar and GtkMenuItem are gone**
- [ ] **GtkToolbar has been removed**
- [ ] **GtkAspectFrame is no longer a frame**
- [ ] **Stop using custom tooltip windows**
- [ ] **Switch to the new Drag-and-Drop api**
- [ ] **Adapt to GtkIconTheme API changes**
- [ ] **Adapt to GtkImage changes**
- [ ] **Update to GtkFileChooser API changes**
- [ ] **Stop using blocking dialog functions**
- [ ] **Stop using GtkBuildable API**
- [ ] **Adapt to GtkAboutDialog API changes**
- [ ] **Adapt to GtkTreeView and GtkIconView tooltip context changes**
- [ ] **Adapt to GtkPopover changes**
- [ ] **Stop using GtkFileChooserButton**
- [ ] **Adapt to changed GtkSettings properties**
- [ ] **Changes to consider after the switch**
- [ ] **Consider porting to the new list widget**
1 Like
Jehan did a lot of work to set up the fiscal sponsorship agreement with GNOME mentioned in their announcement . One aspect of that is to convert the Bitcoin donations into a more “usable” currency to better sponsor developers working on GIMP. I don’t know the status beyond the Bitcoin information being forwarded on, but I believe the plan is to build this out further once 3.0 is released.
2 Likes
veles
(veles worth)
September 18, 2024, 12:57pm
20
GIMP needs more art studios who use only GIMP in production. Krita started to flourish that way because it got more support.