This has always bugged me.

• limit button size so that it does not expand past the delegate height

Forgot to check the album view, buttons are currently too big

• remove unnecessary else

• remove unneeded newline

• cover 1/2 case

In D21830#480181, @bruns wrote:

Many cameras can be switched to 1/2 EV steps.

ping! this now tests the resulting document and tests how the different data types are added to it.

exposure bias seems mostly to be in steps of 1/3 according to https://www.geofflawrence.com/exposure_compensation.html

• rebase on master

• rename to Manufacturer and Model

for the linux part

This needs a frameworks version bump

In D21519#475829, @bruns wrote:

In D21519#475821, @ngraham wrote:

"Camera Manufacturer"?

Well, no ... also "Scanner, Phone, video digitizer, ..."

Digikam just uses "Manufacturer" and "Model", as does Canons DPP

• test decimal value

• remove unrelated change

• directly set the icon width

• cleanup and fix binding loop

before

ping?

@bruns okay for you to merge this one?

• rename format function

• add unit

• only format exposure time

@ngraham what's your take regarding "Manufacturer" vs. "Equipment Manufacturer"?

• change formatting

• implement feedback

• check for zero

Ideally it would be possible to store rationals in KFM and Baloo, but this is probably a lot of work. The computation here is quite simple

In D21520#472882, @ngraham wrote:

Is it really necessary to hide all of these? I don't think any of them are visible by default anyway (the information panel in Dolphin needs to be opened manually) so in general only people who care about detailed information will see this stuff.

• do not hide focal length

Note that I have basically no clue about what is really useful for (hobby) photographers, but these properties look not very useful for the average user to me

If you have a better description for these, please let me know

Are you still interested in working on this? If not, I would like to take over with the following plan:
I would like to propose a transition phase, e.g. we make sure that there is a release available that can handle both formats.
This diff lands with my requested changes.
After the Applications 19.08 release, which can handle both cases, the output format is changed to multiple entries in the property map.
All required patches for the applications have already landed: Elisa (D20502) and Baloo-Widgets (D20739), and Dolphin (D21157)

• remove plainTextContent

• remove isPartOf and hasPart
• use range-based for loop

Before

• also hide photo sharpness

friendly ping

As far as I see from the code, there is only the information from KFileItem, xattr, and baloo/kfilemetadata used in baloo-widgets. Maybe it is a remainder of the KDE4 days?

• use correct camel case names