Gimp 2.9.2 Released
gimp.org
gimp.org
I often open some png or jpeg, edit it and want to save it. But no, I have to export it, confirm that I want to overwrite the file I am editing, and then confirm that I don't want to save to .xcf before closing file or Gimp. Infuriating. It makes me want to fork it just fix this nonsense, but I doubt anyone would want to go into trouble to install my fork. If gimp team don't want to change default behaviour they could at least add a setting to .gimprc: insane_export_behaviour=off. I know I would use it.</rant>
In gimp ctrl+s brings you "save image" dialogue that explictly forbids you from saving anything but XCF, which I too find very annoying when doing quick fixes in batch of graphics that don't have xcf source.
I am baffled why they changed this and why they stick to this decision. But it looks like there is a plugin which fixes that (see one of the other answers), so - yay! :)
And, sure, one can go off and appeal to nature and say "it's standard," but, I really don't buy that argument. There really isn't that much software that deals with the same stuff as GIMP. This isn't like a text editor or something. They are very much in a position to set their own standards when the defacto behaviour is wrong.
In the general sense this is the correct behaviour but in the specific instance of doing simple bitmap manipulation like cropping "export as save" is expected and since thats the most common use case for many people it's probably frustrating.
To be perfectly honest people using gimp for image cropping should use something else, gimp gui is clunky, it starts slowly and there is no benefit.
Maybe this is for you: https://github.com/akkana/gimp-plugins/blob/master/save-expo...
Under Windows, gimp 2.8 has been marginal at best, runs quite slowly, sometimes crashing or freezing, kind of frustrating to use. I downloaded the 2.9 development binary this morning. While still slow, seems a bit faster than 2.8, and didn't crash. More testing will show if this holds up.
I know about people disfavoring workflow of gimp vs. photoshop, but given cost of latter, gimp remains a potentially worthy alternative. It depends on improving the efficiency of operations at least moderately, if so, it looks like the new version of gimp can succeed, even on Windows.
My grandchildren will probably see that.
Well done Gimp devs, and everyone involved.
"Porting plugins to use GEGL buffers simply means that a filter can operate on whatever image data you throw it at, be it 8bit integer or 32bit per color channel floating point. Which is great, because e.g. Photoshop CS2 users who tried 32bit mode quickly learnt they couldn't do quite a lot, until at least CS4, released several years later." http://libregraphicsworld.org/blog/entry/gimp-2-9-2-released
Source: I did the same thing on a much smaller open source project - not only was I still finding things broken up to 4 years later, but fairly early on, turned out I was the main person that understood the code after doing that, so became the maintainer too.
Keep in mind there are "native" apps now for both Gimp and Inkscape (i.e. no longer requiring X11 open and using C- bindings, I'm not sure if for Inkscape it's a fork or what, though, been a long time since I installed it). This has made working with them much better for me.
This is one of the biggest reasons I could never use OSX as my OS.
It's a development release so it was in the Development snapshots section.
Kudos to the Gimp developers and contributors.