Bug 250819 - [KFileMetaDataWidget] Grouping of interconnected information
Summary: [KFileMetaDataWidget] Grouping of interconnected information
Status: RESOLVED WORKSFORME
Alias: None
Product: kfile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdelibs bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2010-09-10 21:11 UTC by Matthias Fuchs
Modified: 2018-10-28 03:22 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Fuchs 2010-09-10 21:11:10 UTC
Version:           unspecified
OS:                Linux

Example: One added two NFO::hashAlgorithm MD5 and SHA-1 and then two NFO::hashValue() as properties to a file.

For the user it is now unclear which hash value is associated with which hash algorithm.

In some cases (MD4 and MD5) just looking at the length of the hash would not solve this issue and also sometimes not the whole hash is being displayed.

Reproducible: Always



Expected Results:  
Ideally the information would be displayed just in one line instead of two:
"[hashAlgorithm] hash: [hashValue]"
e.g.
"MD5 hash: 6eff5b239f07373c15a4a9067c3aedd8"

This issue most likely applies to other ontologies as well so a more general -- less maintance burden -- solution than described above would maybe be needed.

Imo it would be ideally if Nepomuk itself could be used, e.g. associating a hash with a hashAlgorithm. Then the Widget could display any "child" of a property indented. Though I lack the knowledge if that would be possible.
Comment 1 Nate Graham 2018-04-13 15:28:37 UTC
Is this still an issue with KDE Frameworks 5.44 or greater?
Comment 2 Andrew Crouthamel 2018-09-28 03:08:52 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Andrew Crouthamel 2018-10-28 03:22:20 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!