Opened 7 years ago

Last modified 4 years ago

#8687 new enhancement

ShowImage: add "file info" with image properties, exif data, and so on

Reported by: Giova84 Owned by: leavengood
Priority: normal Milestone: R1
Component: Applications/ShowImage Version: R1/Development
Keywords: showimage add file info with exif data and all image properties edit entries Cc:
Blocked By: Blocking:
Has a Patch: no Platform: x86

Description

As the subject said, i suggest to add the voice "file info" inside ShowImage, to show off exif data of photo, geotag info (obviously if present), width, height, year, comment, rating and all available info. And if possible with the option of edit some entries.

Change History (8)

comment:1 Changed 7 years ago by Giova84

To be more clear about the last part: with the option of edit/add/remove info!

comment:2 Changed 7 years ago by axeld

Just as a heads up: the JPEG translator (and probably others?) already return the EXIF data in a BMessage during translation. So at least the read-only part shouldn't be too hard to implement.

comment:3 in reply to:  2 Changed 7 years ago by Giova84

Replying to axeld:

Just as a heads up: the JPEG translator (and probably others?) already return the EXIF data in a BMessage during translation. So at least the read-only part shouldn't be too hard to implement.

Album: http://haikuware.com/directory/view-details/multimedia/graphics/image-viewers/album can do it: http://s11.postimage.org/bj80ys6dv/screenshot1.png

Come with source too..

comment:4 Changed 6 years ago by hometue

(GCI-2012 Participant) Haiku revision: hrev44702. Valid, but this is not a bug. As mentioned, Album from haikuware.com can view EXIF data. System: Haiku R1-alpha4 on Virtualbox 4.1.20 on windows 7 64 bit

comment:5 in reply to:  2 Changed 4 years ago by Janus

Replying to axeld:

Just as a heads up: the JPEG translator (and probably others?) already return the EXIF data in a BMessage during translation. So at least the read-only part shouldn't be too hard to implement.

Hi Axel, the Translator decodes the Exif data into a BMessage but it adds the information as rawdata. Is this on purpose? Would it be more convenient for the applications to have the decoded one?

comment:6 Changed 4 years ago by pulkomandy

If we want to make it "structured" data, we need to define a common format that all translators can use. Having the "raw" data is probably the simpler solution to make sure the interested apps get everything they need from EXIF. I'm not familiar with the EXIF format, does its structure map well with the constraint of a BMessage (is it a tree of typed values)?

comment:7 Changed 4 years ago by Janus

The jpeg translator does already a good job deconding the Exif data into a BMessage:

BMessage(0x0) {
                Maker = string("Canon", 6 bytes)
                Model = string("Canon EOS 5DS", 14 bytes)
                Orientation = int32(0x1 or 1)
                ExposureTime = double(0.00800000)
                ISO = int32(0x64 or 100)
        }

The default tags are only: Maker, Model, Orientation, ExposureTime, ISO. It would be awesome to have the thumbnail in the message and with an input parameter in the ioExtention avoid to translate the full image.

comment:8 Changed 4 years ago by axeld

IIRC you can request a preview using the initial I/O message (might only be implemented by our RAW translator, though).

In any case, it would probably be nice, if the unknown EXIF data would just be added to the message unparsed (EXIF delivers value ID, type, and the actual data). So for example, we could add the tag with ID 7 as "exif:7" with the appropriate type, or just B_RAW_TYPE for everything unsupported.

Alternatively, one could add the whole EXIF data chunk to the message, but that would require parsing it again in the applications.

Note: See TracTickets for help on using tickets.