[Libreoffice-ux-advise] [Bug 98931] Insert images into cells in Calc

https://bugs.documentfoundation.org/show_bug.cgi?id=98931

V Stuart Foote <vstuart.foote@utsa.edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |libreoffice-ux-advise@lists
                   |                            |.freedesktop.org,
                   |                            |vstuart.foote@utsa.edu
          Component|Calc                        |ux-advise
           Severity|normal                      |enhancement

--- Comment #1 from V Stuart Foote <vstuart.foote@utsa.edu> ---
(In reply to cheater00 from comment #0)
> I would like to be able to view images in Calc which are located inside
> cells. As simple as that.

Well, lets see. For starters this would be an Enhancement. Not a bug in any
sense.

Cells can in fact hold images, a simple Insert. But default is to anchor to
sheet (page) --so need to change to anchor to cell for any formatting or
styling of the frame holding the image. Then the image does stay with the cell
with any reformatting or sort.

The frame takes a table:end-cell-address (when anchored to cell), and the image
is either held as binary or as a link.

What is admittedly missing is any handling of a cell's (<table:table-cell>)
<draw:frame> and <draw:image> content as anything more than a rendered image.

What you fail to understand is that this is driven not by LibreOffice
requirements, but instead by requirements in the ODF 1.2 standard as to
function of an OpenDocument Spreadsheet Document the container for Calc
documents we create. 

There are several ways the Exif and other meta details of a source image could
be incorporated into cell attributes--but none are specified in ODF 1.2. There
is no established <table:image> format meaning anything done for LibreOffice
would not transition to other ODF processors.  Even if we extend the .ODS
container for our use, we'd be making an interoperability issue.

Also, most of your use case is already more correctly handled in a database
with SQL column to hold BLOB and meta data of images.

So is this even really a legitimate core requirement? I'd have to say no.

-- 
You are receiving this mail because:
You are on the CC list for the bug.