Bug 99990 - display a warning when there is a tip for reducing the size of an image
Summary: display a warning when there is a tip for reducing the size of an image
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
5.1.2.2 release
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: needsDevEval
Depends on:
Blocks:
 
Reported: 2016-05-22 12:08 UTC by Jérôme
Modified: 2017-10-30 20:53 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
examples of different visual appearances of those warnings (20.17 KB, image/png)
2016-05-22 12:08 UTC, Jérôme
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jérôme 2016-05-22 12:08:07 UTC
Created attachment 125226 [details]
examples of different visual appearances of those warnings

Let us imagine a new user property which defines a resolution limit for images in all printable documents (Writer, Calc, Impress, Draw).

If an image has a resolution which is over the user defined limit then a warning would appear beside the image (or over the image with transparency). When the mouse pointer would be over the warning, the relevant message could be displayed.

Example of relevant messages :
- "the document size will decrease if you reduce the resolution of this image"
- "the document size will decrease if you crop the primary image"
- ...
Comment 1 V Stuart Foote 2016-05-22 12:46:15 UTC
IIUC we already reduce the PPI when exporting to PDF (default 300), and the OS provided print engines will reduce the resolution to what is needed for printing of the document as render to meta on the canvas.

But the actual image is held unchanged in the ODF archive.

So suggestion is just for a user "nag" that an inserted (e.g. not linked) image that will be contained in the archive has a PPI resolution beyond a settable threshold.

Seems feasible, but not clear there is that much value to the enhancement.
Comment 2 MM 2016-05-22 13:55:17 UTC
(In reply to V Stuart Foote from comment #1)

> So suggestion is just for a user "nag" that an inserted (e.g. not linked)
> image that will be contained in the archive has a PPI resolution beyond a
> settable threshold.
> 

Hope that option could be turned off. Already seems annoying to me.
Comment 3 Jérôme 2016-05-22 19:49:21 UTC
At work, my team is writing ODT documents with many pictures. Those documents reach 40 MB of size although they could fit below 5 MB if the resolution of the picture would stay below 300 DPI.

We keep the ODT files on our file server which is backuped (~50 backups spread in daily, weekly and monthly backups). Moreover, our organization has a 5 MB limit for the size of the emails (in a few cases we are working with other persons exchanging ODT files by emails in order to allow modifications).

I don't think the user would be annoyed if the warning is light (the design of the visual interaction has to be clear and simple). Moreover, there is quite no drawback if the user could disable it.
Comment 4 Heiko Tietze 2017-10-30 13:36:00 UTC
Guess you are talking about Format > Image > Compress... that has a size calculation. And you want to show the current size directly at the image to not got into the compression dialog for every image but the large only.

While this sounds like an awesome feature for raster graphic and DTP tools it's IMHO not in-scope for Writer. The feature wouldn't be needed often, is quite error-prone, and slows down the performance. So you better realize this as extension, perhaps with a wizard like the presentation minimizer in Impress.

Adding Tomaz as he made several patches around this feature.
Comment 5 Jérôme 2017-10-30 20:53:14 UTC
In reply to comment #4, the feature I imagine doesn't need to calculate the new size of each image (as performed by the size calculation of "compress..." dialog).

It is just a "dot per inch" (DPI) threshold which highlights the images with a too big DPI. This feature could use a lazy thread in background with quite no performance slowdown (like a spell checker but with lower processing requirements).

A concern of the users in my team is the size of the document they are working on. If they wait until the end of their work before reducing the size of the document, then the more the document is growing the more the computer becomes slow.