English > Feature Suggestions

resize front cover

<< < (2/3) > >>

nostra:
I think I will need to change covers anyway allowing multiple images for each type and more flexible skin manipulations.

rick.ca:
If you did that, it seems to me one image container for both front and CD covers would suffice. But it's the behaviour of the container that makes the difference. Whether it's used for covers or something else, the behaviour of displaying only a thumbnail in the skin—which can be double-clicked to display the full image in the viewer—is a reasonable one. On the other hand, some may want to display a larger version in the skin (e.g., resizing a cover in the skin, just as a poster is now). So if you were to change both these fields so they behave like posters, that would be fine (because the desired behaviour could be specified in the skin), but what about the issue of very large images slowing the drawing of the card?

nostra:
I think I will let users define what they want (thumbnail or original image) in the skin...

buah:
When I was deciding how big my database would be (how many data it should contain) I said to my self: the hardware I'm going to have in the future ain't going to be slower, and I will change it for sure, but for sure I won't re-add additional data to all of my entries because than my hardware could handle it.

In other words, it is more important to me to have a slower but full database at the moment, than to add that very same additional data in the future when hardware getting faster.

nostra:

--- Quote ---In other words, it is more important to me to have a slower but full database at the moment, than to add that very same additional data in the future when hardware getting faster.
--- End quote ---

Original images are still there and you can see them by double clicking the thumbnail, so it is not a problem at all.

Navigation

[0] Message Index

[#] Next page

[*] Previous page