A new 2.9.8 release of @GIMP is now available (windows and macOS builds to follow)!
Have a look at some of the great new features (on-canvas gradient editing, clip warning, wayland support, paste in place, and more)!
It's a bit ironic that it's much easier to install a lot of the FOSS graohics tools and the dev versions of all on Windows and macOS than it is on Linux. 😐
Hopefully that will change soon.
(I wonder if we should start a thread on the forum about it and ask people to help out?)
@garrett @patdavid @GIMP
I don't think flatpak is a solution, there are major issues with that approach and I recommend checking two things to get better idea:
Talk at GUADEC by openSUSE chairman Richard Brown https://www.youtube.com/watch?v=SPr--u4n8Xo
And this blog post about importance of distribution maintainers:
- Darktable with support for my cameras's raw files (currently only available in source)
- unstable Gimp, as it supports high bit depth, etc.
- Rapid Downloader Pro
You can't, because they don't exist. So I have to try compile things from source. Flatpak would solve it.
@GIMP @patdavid @gutigen I've used computers since I was a kid, Linux for more than 2 decades, am a software developer, have worked at Linux companies for nearly 2 decades — and still have problems compiling & updating some of these from source.
Fragmented distros with random DEBs & RPMs (if you're lucky) haven't solved the problems of app distribution. They're also not able to be sandboxed or installed & ran as a user.
This is why we need Flatpak.
What about the majority of people who don't know the first thing about software development? What can they do?
By only releasing tarballs alongside EXEs & DMGs, you're saying to easily run open source software, they should switch to a proprietary operating system!
@garrett @patdavid @GIMP
I trust maintainers more than developers to make sure all security patches and other measures are applied, not to mention compability issues that are not always solved by flatpak (often not from my experience so far).
I think it's important to differentiate between distributions, some might need flatpak cause they have bad packaging toolchain and not enough contributors (and incentives for them), others don't.
I now for sure that Darktable is in #Guix
You could run
guix environment -f path/to/guix.scm
and you'd be in a shell prompt with ALL the Gimp deps available, you could develop Gimp in there
@patdavid @GIMP I haven't been paying attention for a while, so forgive my ignorance, but I wanted to ask: is there a plan in place for consolidating UI? The proliferation of all sorts of plugins (like the excellent G'MIC) with their own UI universes inside GIMP really doesn't help with discovery of various features… Well, I think you guys know about it much better than me :-)
One of the problems with being extremely extensible is possibly having inconsistent UI's across more advanced plugins, like G'MIC.
Part of the problem is that G'MIC is already a pretty full-featured framework for image processing in itself, and usually has different UI requirements than base GIMP might...
@patdavid @GIMP yes, it's probably impossible to solve completely, but it is a kind of problem where small improvements make sense. Like, having UI guidelines ("let's have all blur filters in Filters/Blur", "all preview controls should be of this size and have these buttons attached to them") and encourage authors of prominent plugins to either follow them or provide an API so The Community would write UI for them.
The problems start when there's a non-trivial plugin (again, G'MIC comes to mind). Normally scripts will inherit windowing and controls from GTK and look native to GIMP.
It doesn't help that G'MIC is QT based these days, either. :)