GNOME Bugzilla – Bug 325187
Gnome-screenshot should allow multiple image formats & qualities
Last modified: 2008-07-27 14:49:23 UTC
Gnome-screenshot should at least let people change the quality of their image, and possibly the format. It should be in the gui and not gconf because it can change if people are putting it on different forums or on their own webpage, due to size difference. Other information: The default quality of png is way too big for many forums and it makes me change the quality ot jpeg by opening up in eye of gnome, requiring too many extra steps.
I also often wished for at least some UI to select scale factor (like full, and halved resolution), and that changing the extension of the filename would change the format. Currently it happens sometimes that I create ".jpg" files which are really PNGs.
While I can understand the desire for these features, I do not think they should be included in the GNOME screenshot applet. The screenshot applet is simple and elegant as is. It generates a full-color, full-resolution image of the screen or window that is viewable (though maybe large) in any web-browser. Additional features like scaling and image format are things that can be done better in other applications. Though going to another application requires additional steps, it keeps the basic function of the screenshot applet simple and clear.
I mostly agree: scaling and changing the image quality inside the UI would cripple the simplicity of the tool. as for supporting multiple formats (jpeg and png), I agree with the reporter of the bug: I'd prefer to select the format for the screenshot between lossy (e.g.: for full desktop screenshots) and lossless (e.g.: for single windows). the change in the UI would be pretty minimal, especially since I'd like to make the screenshoter a single FileChooserDialog with a preview widget and solve most of the UI hiccups, like the entry just setting the file name and not the entire path.
I don't think it'll make it for 2.16.x, re-targeting to unspecified.
*** Bug 169450 has been marked as a duplicate of this bug. ***
*** Bug 437146 has been marked as a duplicate of this bug. ***
Bug 521751 has a patch. *** This bug has been marked as a duplicate of 521751 ***