D10803: handle more tags in taglibextractor

[Alexander Stippich]

astippich added a comment.


  In D10803#216118 <https://phabricator.kde.org/D10803#216118>, @michaelh wrote:
  
  > With this many tags we need to be more considerate because it affects other applications which will need to adapt.
  >
  > 1. Plural or singular. E.g. If it was 'performers' the property could reused by video files. (In KF6 the same should apply to 'Languages')
  
  
  While I think you have a point here, KFileMetaData sticked to singular names before, e.g. author, where also multiple persons are possible. So I think we should keep that behavior.
  
  > 1. If there is too much information in them the tooltips in dolphin will refuse to display (not enough room). This behaviour depends on the position of the hovered file relative to the screen. For the same file tooltip sometimes displays sometimes not. That will most likely confuse users.
  
  To be honest, I don't know which tooltip you mean. Can you post a picture? Is this an option I have to switch on?
  
  > 1. The property selection dialog for dolphin's infopanel currently is neat and small. If the list of items in it becomes too long users will have a hard time to find their way through it. We have to check if it needs another layout.
  
  I think it behaves quite well and reasonable with many tags as it shows a scrollbar. I don't think that there is a better solution.
  
  > 1. The property names should be choosen to be as generic as possible to make them reusable by other file types.
  
  I went through the properties again and only found that we might want to use the "generator" property instead of a new "encodedby" property. Do you have any other suggestion?

REPOSITORY
  R286 KFileMetaData

REVISION DETAIL
  https://phabricator.kde.org/D10803

To: astippich, mgallien, ngraham
Cc: vhanda, dfaure, michaelh, ngraham, #frameworks, ashaposhnikov, spoorun, nicolasfella, alexeymin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-frameworks-devel/attachments/20180301/51eeba6a/attachment-0001.html>