Bug 358571 - Information panel could display some information in a more compact way
Summary: Information panel could display some information in a more compact way
Status: RESOLVED NOT A BUG
Alias: None
Product: baloo-widgets
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Pinak Ahuja
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-26 08:32 UTC by Michael D
Modified: 2020-04-30 10:20 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Screenshot of issue (162.37 KB, image/jpeg)
2016-01-26 08:33 UTC, Michael D
Details
mockup for 1 column layout (370.61 KB, image/jpeg)
2018-01-08 12:23 UTC, Marijo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Michael D 2016-01-26 08:32:51 UTC
When the information panel is set to be relatively narrow, which I assume is a common configuration, the information is not efficiently displayed when there are comments, due to the dual column nature. I've attached a screenshot showing this.

The information would be better displayed under one column, with the headings "Tags", "Ratings", etc. appearing e.g. centered and bolded. E.g. instead of

Comment: Lewis's
                  amendment to
                  the simple
                  conditional
                  analysis

we would have
       <b>Comment</b>
Lewis's amendment to the
simple conditional analysis

Perhaps this is better marked as a wish rather than bug.

Reproducible: Always
Comment 1 Michael D 2016-01-26 08:33:25 UTC
Created attachment 96846 [details]
Screenshot of issue
Comment 2 Frank Reininghaus 2016-01-29 22:25:38 UTC
Thanks for the bug report. Baloo's MetaDataWidget is responsible for displaying this information, so I'll reassign.
Comment 3 Michael D 2016-03-12 09:11:47 UTC
Thinking about this issue again, the information is most efficiently displayed in dual column as long as no comments are added. I wonder if comment information is the only information that can be displayed in a single-columns.
Comment 4 Marijo 2018-01-08 12:23:41 UTC
Created attachment 109732 [details]
mockup for 1 column layout

I made a mockup how a 1 column based layout may look like. Personally I like it a lot and it offers much more space for the important informations.
Comment 5 Michael D 2018-01-08 14:40:20 UTC
I like Marijo's mock-up. I suppose there is room for further streamlining. E.g., it is obvious that the stars correspond to a rating so the heading "Rating:" doesn't need to be there; the rating could occur first at the top without a heading, while tags and comment occur below with headings.
Comment 6 Stefan Brüns 2020-04-15 13:33:08 UTC
The mockup wastes space when there are many properties each fitting in a single line, e.g. common for images with exif data.

So this optimizes for one use case, disregarding any other.
Comment 7 Bug Janitor Service 2020-04-30 04:33:11 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
mark the bug 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 8 Christoph Feck 2020-04-30 08:18:11 UTC
Stefan, could you please state which information is needed to resolve this ticket?
Comment 9 Stefan Brüns 2020-04-30 10:15:08 UTC
First, this is more a feature request than a bug
Comment 10 Stefan Brüns 2020-04-30 10:20:18 UTC
First, this is more a feature request than a bug report - it works as designed, and has been designed as is for the reasons I stated in #c9.

This would have been enough reason to directly close it. As I wanted to know if the reporter or anyone else wants to work on a solution which improves the design for all cases, I set it to NEEDSINFO.

Due to lack of any reaction closing now.