|
Hi all, I've been playing a little with how to properly indicate, that some images have other versions. I've come up with two cases - the first case is when you have only the last/current version visible and the rest is hidden and the second case is when you have all the images visible regardless of relation (there is an option for this hiding/showing)
In the first case, I made a "stack" (or a pile if you will, see screenshot 1) of images, you can switch the images in the sidebar, that will set the "current" flag to that switched image (please note that the other versions are not hidden in this, this is still work-in-progress).
In the second case, all images that belong into one relation are outlined in the icon view. See screenshot 2. What do you think about this? Please remember that these are just mockups (ready to commit though) and I'd like to hear your opinions, especially about the second one (is it good/bad/what colors should be used etc).
Screenshot 1 - http://www.flickr.com/photos/mck182/5146385372/ Screenshot 2 - http://www.flickr.com/photos/mck182/5146385234/
(zoom in for better view) Thanks, Marty
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
> I've been playing a little with how to properly indicate, that some images > have other versions. I've come up with two cases - the first case is when > you have only the last/current version visible and the rest is hidden and > the second case is when you have all the images visible regardless of > relation (there is an option for this hiding/showing) > > In the first case, I made a "stack" (or a pile if you will, see screenshot > 1) of images, - there is no (0px) spacing left in the upper and left edges of the pile. One pile element less? - the main element border is lighter than the pile borders > you can switch the images in the sidebar, that will set the > "current" flag to that switched image (please note that the other versions > are not hidden in this, this is still work-in-progress). When we implement this, as discussed, in the ImageFilterModel, we will be able, through some whitelisting, to "fan out" a pile dynamically > > In the second case, all images that belong into one relation are outlined > in the icon view. See screenshot 2. Is this drawn only when one item of the group is selected? The colors are suggestive of that. In any case, colors must be taken from the theme. Is it possible to draw the "edges" (left side first picture, right side last picture of group) differently? Perhaps some rounded rects and or gradients. I'm not a designer, I can only say if I like something when I see it, I dont know how to code what I like in advance ;-) _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
On Thu, Nov 4, 2010 at 19:28, Marcel Wiesweg <[hidden email]> wrote:
Yes, I was thinking to either increase the spacing (not a good approach really) or to do only two elements. Probably will go with two. - the main element border is lighter than the pile borders I can't seem to find the color with which the main rectangle is painted, so I used Qt::gray for the while. But they will definitely match at the end.
That's exactly what I was thinking :)
Yes, when you select any one image inside one relation cloud, all of them gets outlined. The color is again just for testing purposes, but I wouldn't use theme's color for selection, because then you won't easily recognize, which image you have selected. So we should make it either lighter/darker/more contrast/perhaps inverse?
I'd like to do something like that, to paint one polygon-thing around all of the outlined images, but that would need some heavy "if-ing", also I'm not sure if you can tell from one item that is being painted if the next item is also in the group. But I will investigate this and we'll see.
Thanks for the input! Marty _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
In reply to this post by Martin Klapetek
The first solution is interresting because it's save sapce in
icon-view. But, there is a problem to know how many image are in the stack. Perhaps a valur indicator over the icon can be a solution. Also, how to select quickly a version from the stack ? The second way sound like better to play with stack item. also, we can apply icon view filter directly. This solution use more space in icon view, but with items filters, stck content can be managed very well. On my mac, i installed Aperture and LightRoom. I can take a look how stack is managed from icon view. Gilles Caulier 2010/11/4 Martin Klapetek <[hidden email]>: > Hi all, > I've been playing a little with how to properly indicate, that some images > have other versions. I've come up with two cases - the first case is when > you have only the last/current version visible and the rest is hidden and > the second case is when you have all the images visible regardless of > relation (there is an option for this hiding/showing) > In the first case, I made a "stack" (or a pile if you will, see screenshot > 1) of images, you can switch the images in the sidebar, that will set the > "current" flag to that switched image (please note that the other versions > are not hidden in this, this is still work-in-progress). > In the second case, all images that belong into one relation are outlined in > the icon view. See screenshot 2. > What do you think about this? Please remember that these are just mockups > (ready to commit though) and I'd like to hear your opinions, especially > about the second one (is it good/bad/what colors should be used etc). > Screenshot 1 - http://www.flickr.com/photos/mck182/5146385372/ > Screenshot 2 - http://www.flickr.com/photos/mck182/5146385234/ > (zoom in for better view) > Thanks, > Marty > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
On Sat, Nov 6, 2010 at 14:54, Gilles Caulier <[hidden email]> wrote:
The first solution is interresting because it's save sapce in Yes, that could be done, probably. Although I would leave it to show only on mouse over, like the rotate buttons. Also this gives me an idea to put a number of versions somewhere in the versioning sidebar, so you can easily see how many versions you have available.
Also, how to select quickly a version from the stack ? That is done from the sidebar - you select the stack and the sidebar shows all the available versions and you simply select which version you want. This version will then stay on top of the stack.
The second way sound like better to play with stack item. also, we can Both solutions will be actually used. You have an option to either show only one image from all versions and hide the rest (the stack) or to leave them all displayed in icon view (the outline). So they are both implemented. There's just a small problem on how to make the outline look good visualy, because the delegate has no information about the items around, so you can't paint one thicker line around all the images for example. It could be done by using some heuristics, but I'm afraid that this would add too much complexity and would slower things down. I'll see what could be done though.
Yes, please do :) Marty _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
For LR, look this page :
http://dpexperience.com/2010/03/05/un-clutter-your-library-with-lightrooms-stacks/ Gilles 2010/11/6 Martin Klapetek <[hidden email]>: > On Sat, Nov 6, 2010 at 14:54, Gilles Caulier <[hidden email]> > wrote: >> >> The first solution is interresting because it's save sapce in >> icon-view. But, there is a problem to know how many image are in the >> stack. Perhaps a valur indicator over the icon can be a solution. > > Yes, that could be done, probably. Although I would leave it to show only on > mouse over, like the rotate buttons. Also this gives me an idea to put a > number of versions somewhere in the versioning sidebar, so you can easily > see how many versions you have available. > >> >> Also, how to select quickly a version from the stack ? > > That is done from the sidebar - you select the stack and the sidebar shows > all the available versions and you simply select which version you want. > This version will then stay on top of the stack. > >> >> The second way sound like better to play with stack item. also, we can >> apply icon view filter directly. >> >> This solution use more space in icon view, but with items filters, >> stck content can be managed very well. > > Both solutions will be actually used. You have an option to either show only > one image from all versions and hide the rest (the stack) or to leave them > all displayed in icon view (the outline). So they are both implemented. > There's just a small problem on how to make the outline look good visualy, > because the delegate has no information about the items around, so you can't > paint one thicker line around all the images for example. It could be done > by using some heuristics, but I'm afraid that this would add too much > complexity and would slower things down. I'll see what could be done though. > >> >> On my mac, i installed Aperture and LightRoom. I can take a look how >> stack is managed from icon view. > > Yes, please do :) > Marty > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
In reply to this post by Martin Klapetek
> because the delegate has no information about the items
> around, so you can't paint one thicker line around all the images for > example. It could be done by using some heuristics, but I'm afraid that > this would add too much complexity and would slower things down. I'll see > what could be done though. How do you trigger the painting of the border at all? mouse over -> find related images -> pass a special flag to the delegate when painting? The view will know the left and right edge of this "selection" (which need not be contiguous btw) > For LR, look this page : > > http://dpexperience.com/2010/03/05/un-clutter-your-library-with-lightrooms- > stacks/ The "icon" solution would be an alternative to the current stack. Advantage: It does not disturb the visual appearance as much; it provides a space to click on. But not on the thumbnail, preferably below in the information area? Or in a bottom corner? and not larger than two characters in the smallest readable font. > I can't seem to find the color with which the main rectangle is painted, so > I used Qt::gray for the while. But they will definitely match at the end. Have a look at ThemeEngine. The pixmap is prerendered there, there's a border color. It's probably not publicly available atm, but could. _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
On Sat, Nov 6, 2010 at 18:48, Marcel Wiesweg <[hidden email]> wrote:
Currently it's not on mouse over, but just on click, so you select the image, then it checks if it is in current relation (QList added to ImageDelegate), if yes, then just paint part of the border, if not, the get the relation cloud from DB, turn it into simple QList<qlonglong>, store it, paint the border. I can get an index for sibling and then get its id with ImageInfo::getImageId(index) and see if it is in the relation, but that's just a sibling in the model, not in the view, as you said, they sometimes aren't continuous. I suppose I could get even the top/bottom siblings by moving the index by currentColumn+columnsInRow, not sure what that will do though. I'll play with it a little and see what I'll come up with.
Agreed. Maybe even the top-left corner? But definitely not over the thumbnail.
Ok, great, thanks! Marty _______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
Ok, so I figured out the outline for all the versions. Look here --> http://www.flickr.com/photos/mck182/5171745110/
Yeah it still has some glitches (which are being fixed right now), but basically it works! The outline is preserved even when you change the zoom ratio or when you're working with sidebars (expand/collapse). The outlines are selected directly in the delegate, so if anything changes the view in any way, the delegate will redraw everything and thus reselect the correct edges.
Now how about the coloring? I don't want to use the "selected" color for this as that would confuse the user and it would not be possible to see, which image is selected. We could make it either inverse color of current "selected" theme color, but that could lead to some very wild and just wrong colors with some themes, or to use lightgray. It will be just lightly outlined, suggesting the relation in an nondisturbing way.
What do you think? Marty
_______________________________________________ Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
|
Hum, how i can interpret it exactly?
The first time that i see this shot, i have been perturbated : what i must see there... After reflexion, i understand that all item are grouped due to versionning. How i can see how many items are grouped exactly ? (without to take a look into right sidebar of course) ? I think the group color use to identify versioned items is not ideal... But it my viewpont of course... Gilles Caulier 2010/11/13 Martin Klapetek <[hidden email]>: > Ok, so I figured out the outline for all the versions. Look here > --> http://www.flickr.com/photos/mck182/5171745110/ > Yeah it still has some glitches (which are being fixed right now), but > basically it works! The outline is preserved even when you change the zoom > ratio or when you're working with sidebars (expand/collapse). The outlines > are selected directly in the delegate, so if anything changes the view in > any way, the delegate will redraw everything and thus reselect the correct > edges. > Now how about the coloring? I don't want to use the "selected" color for > this as that would confuse the user and it would not be possible to see, > which image is selected. We could make it either inverse color of current > "selected" theme color, but that could lead to some very wild and just wrong > colors with some themes, or to use lightgray. It will be just lightly > outlined, suggesting the relation in an nondisturbing way. > What do you think? > Marty > > _______________________________________________ > Digikam-devel mailing list > [hidden email] > https://mail.kde.org/mailman/listinfo/digikam-devel > > Digikam-devel mailing list [hidden email] https://mail.kde.org/mailman/listinfo/digikam-devel |
| Free forum by Nabble | Edit this page |
