<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi,<div class=""><br class=""></div><div class="">thanks for the feedback. There was also a PNG screenshot attached to my email which showed the original layout.</div><div class="">Regarding your comments:</div><div class=""><br class=""></div><div class="">1: This is not a left-side (= filter) sidebar but a right-side (= editor) sidebar. So clicking on the date should modify the selected image(s)’s date(s). „Select by date“ already exists on the left side of Digikam’s main window. If multiple images are selected, this should show a date range and editing this might even be used to shift dates (with a confirmation dialog asking whether to set all dates to the same value or to use the first selected image as base date and use the delta to shift all dates - just like the extra wizard does now).</div><div class=""><br class=""></div><div class="">2: Ratings are shown to the right of the filename. Basically just like now only that the basic image metadata isn’t spread over five different tabs.</div><div class=""><br class=""></div><div class="">3: The tags tree should stay. My original idea was not to replace multiple existing editing tabs but to only replace the (redundant) first one called „Properties“. I was looking for a quick and compact way to view and edit common metadata of selected images explicitly *without* having to use the tree. If selected images have a non-unique set of tags, the tag input field should reflect this (either show non-unique tags greyed out or something like that).</div><div class=""><br class=""></div><div class="">But coming to think of it, this dashboard would have the potential to clean up the whole right sidebar. Here’s my thoughts:</div><div class=""><br class=""></div><div class="">„Properties“:<span class="Apple-tab-span" style="white-space: pre;"> </span>replace<span class="Apple-tab-span" style="white-space: pre;"> </span>This can be completely replaced. As of now I do not see any use case that isn’t covered.</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Plus we save lots on translation strings we don’t need any more.</div><div class="">„Metadata“:<span class="Apple-tab-span" style="white-space: pre;"> </span>keep<span class="Apple-tab-span" style="white-space: pre;"> </span>This is a „more details“ version of Properties. It would stay.</div><div class="">„Colors“:<span class="Apple-tab-span" style="white-space: pre;"> </span>keep<span class="Apple-tab-span" style="white-space: pre;"> </span>This - for me - is nothing I use often (I use it on my camera often, but not in Digikam).</div><div class="">„Map“:<span class="Apple-tab-span" style="white-space: pre;"> </span>remove<span class="Apple-tab-span" style="white-space: pre;"> </span>The map would become part of the dashboard. Smaller, though.</div><div class="">„Captions“:</div><div class=""> Description<span class="Apple-tab-span" style="white-space: pre;"> </span>remove<span class="Apple-tab-span" style="white-space: pre;"> </span>- contains most of what the Dashboard will contain too.</div><div class=""> Tags<span class="Apple-tab-span" style="white-space: pre;"> </span>keep<span class="Apple-tab-span" style="white-space: pre;"> </span>- contain the tag tree and an entry field. The tree by itself won’t be replaceable.</div><div class=""> Information<span class="Apple-tab-span" style="white-space: pre;"> </span>keep<span class="Apple-tab-span" style="white-space: pre;"> </span>- contains IPTC information about the author. Also not replaceable.</div><div class="">„Versions“:<span class="Apple-tab-span" style="white-space: pre;"> </span>keep<span class="Apple-tab-span" style="white-space: pre;"> </span>This is not covered.</div><div class="">„Filter“:<span class="Apple-tab-span" style="white-space: pre;"> </span>keep<span class="Apple-tab-span" style="white-space: pre;"> </span>Also not covered.</div><div class="">„Extras“:<span class="Apple-tab-span" style="white-space: pre;"> </span>don’t know, these are tools that - IMHO - only belong into a menu, not an icon view.</div><div class=""><br class=""></div><div class="">I updated my mockup in the attachment plus added a screenshot so you can view it even without the correct fonts).</div><div class=""><br class=""></div><div class=""></div></div></body></html>