Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

GIMP 2.9.4 and our vision for the future

girinstud.io

Post reply on HN
Print view View original

91–98 of 98 posts

Re: GIMP 2.9.4 and our vision for the future

#91

Post by userbinator »

unabst wrote: post #88
userbinator wrote: post #46

Earlier quoted context omitted.

Photoshop will save in the original format unless you do something to the image that isn't supported in that format (e.g. adding vectors, layers, layer filters, etc.) Then it will switch to .psd, although you still get the option of saving in the original format with Save As. I think that is a good design.

What would be better is having a dialog that says "You've used some additional features that can only be saved in .psd format: Save as PNG || Save as PSD || Save as something else" with the first being the default for when you press ENTER.

Microsoft Word does that, and indeed the default is the original format.

"%s may contain features that are not compatible with %s. Do you want to save the document in this format?

To save, click Yes. To preserve formatting, click No. Then save a copy in the %s format."

Re: GIMP 2.9.4 and our vision for the future

#92

Post by Jehan-Girin »

babuskov wrote: post #84
imurray wrote: post #27

Earlier quoted context omitted.

I totally see that it makes sense for some work flows, including the ones Gimp is probably most meant for. It was frustrating that for the people whose workflows were messed up, the developers were totally opposed to doing anything about it though. Kudos to the plugin author for rolling up her sleeves and providing a way out. Also kudos to the gimp developers for providing a plugin architecture that made such a custo…

If they made Ctrl-E work when you load the file for the first time, none of this would be the problem.

I don't understand. Ctrl-e does work fine "when you load the file for the first time".

Even to make extra sure (though I already was), I have tested it on a GIMP 2.8 and on GIMP master just now. That works.

Re: GIMP 2.9.4 and our vision for the future

#93

Post by unabst »

userbinator wrote: post #91
unabst wrote: post #88

Earlier quoted context omitted.

What would be better is having a dialog that says "You've used some additional features that can only be saved in .psd format: Save as PNG || Save as PSD || Save as something else" with the first being the default for when you press ENTER.

Microsoft Word does that, and indeed the default is the original format. "%s may contain features that are not compatible with %s. Do you want to save the document in this format? To save, click Yes. To preserve formatting, click No. Then save a copy in the %s format."

Right. But the difference here is you need to answer the question which is a task. Then based on what you actually want to do, there is an extra step in opening the dialog just to choose the other format etc.. maybe you just want to save in the application default. The point of the version I posted is that each button maps to a direct intention. The message is informative, and the user does what they want. It's not the application asking or warning or assuming anything. It's not the developer imposing anything. Based on what the application can do, the user is presented with the various options that map to intentions.

Re: GIMP 2.9.4 and our vision for the future

#94

Post by woliveirajr »

StevePerkins wrote: post #34
imurray wrote: post #20

Gimp 2.8 frustrated me: I could no longer open a .png, edit it and easily resave it back to .png. The Gimp developers knew better and made the UI strongly favor saving as .xcf, which makes sense in some use-cases, but not mine. I found this fix, which made quick uses of GIMP less painful for me: http://shallowsky.com/software/gimp-save/ I'm assuming the new save behavior persists in Gimp 2.9.x, but I don't know.

> less painful for me I realize that this is common UX jargon, but is it literally "painful" to click "File->Export" rather than "File->Save"? I frequently hear front-end developer peers arguing that it's "painful" to read 10 or 20 lines of XML. Back-end peers retort that it's more "painful" to look at large complex structures in JSON. There's a hundred other cases in which this comes up. Are people really walking ar…

Yes it is.

If I open a .png, and done things to it, and I want to save it, it's because I just want to save a .png. If I wanted to have another format I would "import" the .png, not open it.

If I want to save something else, then I'll go to the save as... And will choose what I want to save.

Having a "save as..." that just gives me the proprietary format and hanging to go to the "export as..." to have other formats is even worst.

Re: GIMP 2.9.4 and our vision for the future

#95

Post by babuskov »

Jehan-Girin wrote: post #92
babuskov wrote: post #84

Earlier quoted context omitted.

If they made Ctrl-E work when you load the file for the first time, none of this would be the problem.

I don't understand. Ctrl-e does work fine "when you load the file for the first time". Even to make extra sure (though I already was), I have tested it on a GIMP 2.8 and on GIMP master just now. That works.

Here, I recorded a video to show the problem:

https://www.youtube.com/watch?v=SekYlC4ON_U

I tried with 2.8.14 and 2.8.18, both running on Mac OSX. As you can see the Command-E option only shows up after I do "Export as".

Re: GIMP 2.9.4 and our vision for the future

#96

Post by prokoudine »

phkahler wrote: post #49

Still waiting. They need to prioritize 3 things IMHO, and those are 1) GEGL integration - this was claimed to be 80 percent done in 6 weeks (several years ago). Updating core code and libraries should be done quickly, not spread out over years concurrently with other development. 2) Update to GTK3. How can a flagship OSS program still be using a many-years-old GUI toolkit? And finally 3) Wayland support. This will be…

You mean completing and releasing 2.10 should be a 4) in your list? :D

Re: GIMP 2.9.4 and our vision for the future

#97

Post by schumaml »

babuskov wrote: post #95
Jehan-Girin wrote: post #92

Earlier quoted context omitted.

I don't understand. Ctrl-e does work fine "when you load the file for the first time". Even to make extra sure (though I already was), I have tested it on a GIMP 2.8 and on GIMP master just now. That works.

Here, I recorded a video to show the problem: https://www.youtube.com/watch?v=SekYlC4ON_U I tried with 2.8.14 and 2.8.18, both running on Mac OSX. As you can see the Command-E option only shows up after I do "Export as".

Did you try whether it works? If this was in your video, I didn't see it.

Re: GIMP 2.9.4 and our vision for the future

#98

Post by babuskov »

schumaml wrote: post #97
babuskov wrote: post #95

Earlier quoted context omitted.

Here, I recorded a video to show the problem: https://www.youtube.com/watch?v=SekYlC4ON_U I tried with 2.8.14 and 2.8.18, both running on Mac OSX. As you can see the Command-E option only shows up after I do "Export as".

Did you try whether it works? If this was in your video, I didn't see it.

I tried, and even filed a bug report. It's "as designed":

https://bugzilla.gnome.org/show_bug.cgi?id=769359

The whole idea around this and the way they decided it to work is a mess.

Post reply on HN