Hacker News new | comments | ask | show | jobs | submit login

Really not a fan of this. In a link he says he took the code for saving/exporting and split it apart: http://girinstud.io/news/2015/09/improving-the-export-proces...

The only way I ever use GIMP is through forked builds that let you save as whatever you want without the annoying save/export distinction, so they seem to making it tougher for people who are making good forks of their bad software to do their job.




Saving and exporting are different tasks: the former saves the current work-in-progress project with no loss of data, the latter exports to a particular image format and is inherently lossy. If you combine them, you risk misleading users.

And by keeping them split, it makes some things more convenient. When I edit images, I save a .xcf and I also export a .png. Having to manually switch between these file-types and manually remember and re├źnter the (possibly differing) filenames when saving would be a pain. Keeping Export and Save as separate means I don't have to. It also means that Ctrl-S saves the project, rather than overwriting my last export. And as the part you linked to points out, this means you can do things like change the scale at export time.


What's the difference, and why should it matter? I just want to persist my changes to a file.

IMHO just keep things simple and use Save for saving in the same format as the original (possibly if a warning if it doesn't support some things you've done to the file), or Save As for saving in a different format.


Simply, you expect Open > Save to persist your file format. In the use case they target Save > Open persist what you were editing. Things like Live Text, Smart Objects, alpha layers (for many file formats), etc will stay around. It's a common approach I've seen in other image editors (including Photoshop), 3d tools, and I imagine text editors do this, too.


> What's the difference, and why should it matter?

See edits.

> IMHO just keep things simple and use Save for saving in the same format as the original (possibly if a warning if it doesn't support some things you've done to the file)

You'd have to warn on every single format except XCF.

> or Save As for saving in a different format.

But I don't want to change the save destination. The project and the export are separate for me.

If you just want to save a PNG or something, you have the option of using Export exclusively.

But I need the ability to Save.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: