

















After the first round of community feedback, we’re happy to share the second release candidate for GIMP 3.0! People gave us really helpful feedback from the first release candidate and we were able to fix a lot of bugs.
It is our little under-the-tree 🎄 present for you all!
There have been a number of fixes since RC1. We want to highlight the most impactful bugs so that users are aware and can provide additional testing. For details on other bug fixes, please check our NEWS page in GitLab.
During community testing, we discovered that user’s 2.10 settings were not being migrated to GIMP 3.0 due to some incorrect assumptions in the import code. Since most of the developers have been using GIMP 3.0 exclusively for some time, we did not notice this issue. The bug should now be fixed, so we ask for bug reports if any 2.10 preferences are not being imported correctly in RC2. Note that if you already used 3.0 RC1, you’ll need to delete those configurations first, as otherwise RC2 won’t try to import the 2.10 preferences (make sure you back up your settings of course!)
In the 2.99 development releases, the Windows versions automatically launched a console display in addition to GIMP itself. This is very useful for Windows developers to see debug messages, but the console was not intended to be shown during stable releases. Since we changed our build process to use Meson instead of Autotools, we learned we needed to make additional changes to stop the console from being displayed. This should be fixed now thanks to Jehan - if you still see the console on Windows, please file a new bug report!
There has been a long-standing issue where some macOS users only saw “missing Unicode” symbols instead of menu text in GIMP (both in 2.10 and in 3.0). This was due to a bug in Pango, the library we use for text layouts. This was fixed with the recent Pango 1.55.0 release, so we encourage all third-party macOS packagers to update to this version as they build GIMP for distribution.
After the 3.0 RC1 release, we received reports from some users that they still could not import and export images between GIMP and darktable. We worked with the darktable developers to iron out the remaining bugs, so integration between darktable 5.0.0 and GIMP 3.0 RC2 should be working for everyone now. However, please file a new bug report if you continue to have trouble connecting the two!
While the main focus of 3.0 RC2’s development was bugfixes and polish, some new features were also implemented.
Many of the older API wrappers for GEGL operations were removed in RC1. While this reduced technical debt, it also caused issues for many third-party plug-in and script developers who wanted to port their plug-ins to 3.0. While our initial plan was to implement the new public filter API after the 3.0 release, the feedback from the community convinced us to add it in for 3.0 RC2.
Jehan‘s work allows developers to apply filter effects either immediately or as a non-destructive effect.
You can see examples of how to do this in C, Python, and Script-Fu in the
merge request, or by looking up gimp-drawable-filter
in the Procedure Browser inside GIMP. We’ve also begun using the filter
API in our Python scripts to automatically create blurred background
effects
for the Windows installer, and with this same API in C, Alx Sa added support
for importing
Photoshop’s legacy Color Overlay layer
style.
We ask for feedback and bug reports from plug-in and script authors who utilize the new filter API in their work! We have more updates planned for it in GIMP 3.0 as well.
Discussions between color science experts Elle Stone and Øyvind Kolås revealed another area that needed improvement as part of our Color Space Invasion project. Specifically, images with color profiles that have non-perceptual TRCs might not be rendered correctly when set to certain layer modes.
Øyvind has implemented a correction for this problem by adding proper perceptual space as default to specific layer modes. While we believe this enhancement should not impact older XCF files, we of course want to hear from you if there are any backwards compatibility issues with 3.0 RC2!
Thanks to the continued efforts of Bruno Lopes and with assistance from Samueru and the AppImage community, our experimental AppImage now works on most Linux distros. We want to encourage more testing of it, in hopes that we can offer it as another Linux release in addition to our Flatpak. You can see instructions to install experimental AppImage packages from our development download page.
Our nightly flatpak has now a dedicated App-ID org.gimp.GIMP.Nightly.
This mostly means that it can be installed side by side with the stable
flatpak while both are visible in your menus (no need to select which
version is to be shown with flatpak make-current anymore).
Yet it also means that anyone who had the nightly flatpak until now won’t see any update coming anytime soon. In order to continue using the nightly flatpak, uninstall the existing one and install the new one with these commands:
flatpak uninstall org.gimp.GIMP//master
flatpak install https://nightly.gnome.org/repo/appstream/org.gimp.GIMP.Nightly.flatpakref
⚠️ Reminder: the nightly flatpak is current development code as it happens in source repository. At times, it may even be very broken or render your project files invalid. We do not recommend it for production! Use this version to help us debugging by reporting issues or if you really like risks to test latest features.
New contributor Rupert Weber has been busy since the last update with more updates to our BMP plug-in. A few highlights of their work:
Alx Sa implemented loading CMYK PAM files in the PNM plug-in.
On Windows, we’ve also added the ability to open images through
Windows Shortcuts (.lnk files) directly from the file chooser dialog.
This is also work by Alx Sa.
More tweaks and improvements have been made to the theme. In particular, the slider styling has been substantially improved after feedback and work from Denis Rangelov. Denis also made new icons for the Navigation Dockable Dialogue, replacing duplicates with distinct symbols. Anders Jonsson has also been reviewing the theme and removing some workarounds which were required in GIMP 2.10, but no longer needed with our new 3.0 themes.
Idriss Fekir has made improvements to our XCF font loading code, to improve compatibility when importing older XCF files.
For those who haven’t followed GIMP’s development as closely, these news posts only cover incremental changes since the last release. They do not list every change or improvements made for GIMP 3.0 - that would be a very long article indeed!
While we’ll have full release notes for the final 3.0, we thought it’d be helpful to summarize a few of the major changes made during the 2.99 development process:
/ search
pop-up was updated to show the menu path for all entries, as well as making individual filters searchable.Similar to GIMP, there’s a number of bugfixes for the GEGL 0.4.52 release. Øyvind Kolås has fixed some generic “Aux input” labels to be more meaningful - this will be visible in GIMP’s filters as well. He also improved the accuracy of some filter’s color processing. Longtime contributor Thomas Manni also fixed crashes when some filters were run on very small layers.
Since GIMP 3.0 RC1, in the main GIMP repository:
35 people contributed changes or fixes to GIMP 3.0.0 RC2 codebase (order is determined by number of commits; some people are in several groups):
Contributions on other repositories in the GIMPverse (order is determined by number of commits):
gimp-data had 6 commits by 5 contributors: Anders Jonsson, Jehan,
Sevenix, Alx Sa and Denis Rangelov.gimp-test-images (new repository for image support testing) had 2
commits by 1 contributor: Rupert.gimp-macos-build (macOS packaging scripts) release had 5
commits by 1 contributor: Lukas Oberhuber.Let’s not forget to thank all the people who help us triaging in Gitlab, report bugs and discuss possible improvements with us. Our community is deeply thankful as well to the internet warriors who manage our various discussion channels or social network accounts such as Ville Pätsi, Liam Quin, Michael Schumacher and Sevenix!
Note: considering the number of parts in GIMP and around, and how we
get statistics through git scripting, errors may slip inside these
stats. Feel free to tell us if we missed or mis-categorized some
contributors or contributions.
GNOME has moved away from using mirrors during their latest infrastructure update. As our download mirrors are hosted by them, we were asked if we wanted to move as well. As a community project, we value everyone who contributes a mirror to make GIMP more accessible in their area. Therefore, we have decided to stay with using mirrors to distribute GIMP.
If you are interested in contributing a mirror for your region, here is the new procedure:
🛈 We programmatically check at random intervals that mirrors are updated quickly enough and that the data match for obvious security reasons.
Also, since the 3.0RC1 news post, a new mirror has been contributed:
Mirrors are important as they help the project by sharing the load for dozens of thousands of daily downloads. Moreover by having mirrors spread across the globe, we ensure that everyone can have fast download access to GIMP.
GIMP’s code repository is also hosted on GNOME’s GitLab platform. Andrea Veri asked if we would be able to sponsor a runner on the platform, which allows any project on the platform to test building their software before, during, and after code changes are made. After a vote by GIMP’s committee, we agreed and are now the sponsors of an x86 CI/CD runner!
You will find all our official builds on GIMP official website (gimp.org):
Other packages made by third-parties are obviously expected to follow (Linux or *BSD distributions’ packages, etc).
🛈 Notes:
Thanks to the huge amount of reports we got for our first release candidate, we are able to present you this second version which is all the more robust. As you saw, a few additional surprises 🎁 came together with bugfixes, in particular the new filter API, which triggered support of PSD legacy Color Overlay import, improved blend modes and compositing, and more. We thought that it was worth breaking the feature freeze for these changes and that this will make all the difference!
With this second release candidate, we are closer than ever to actual GIMP 3.0.0. As usual, we are looking forward to any new community issue reports allowing us to finalize the 3.0.0 release! 🤗
Don’t forget you can donate and personally fund GIMP developers, as a way to give back and accelerate the development of GIMP. Community commitment helps the project to grow stronger! 💪🥳
🎅🎄🎉 Oh and of course, the whole team wishes you all a happy holiday season! 🥳🥂🎆
此内容由惯性聚合(RSS阅读器)自动聚合整理,仅供阅读参考。 原文来自 — 版权归原作者所有。