Skip to content

Conversation

@IBBoard
Copy link
Contributor

@IBBoard IBBoard commented Aug 9, 2016

My proposal to balance "I don't want tall images" with "I like media and run Corebird really wide" in Bug #465.

These changes make the visible part of the media render at max 4:3 proportions (chosen because they're old monitor proportions, fairly square and hence don't make you go "huh? what size/shape is that?", and still quite common for images based on what I saw in my timeline).

If the image is too wide then Corebird will scale the image (as it does now).

If the image is too tall then Corebird will show the middle of the image.

If the widget's bounding box is wider than the image then Corebird uses 4:3 proportions on the bounding box to calculate the max height, which will allow portrait images to show more height. (But if the image is landscape then the box won't grow too tall)

IBBoard added 5 commits August 9, 2016 20:12
Keep 4:3 proportions where we can.

Currently doesn't:
 * crop image height
 * middle-align the cropping
 * work correctly with multiple images
Images that are greater than app width and portrait are cropped correctly
Images narrower than app width but portrait aren't cropped correctly
Images that are small enough are okay
Images that are wider than app width but not 4:3 tall have spacing
We now show the middle of the image

Height is max 4:3 proportions of the widget
 * Fix code formatting
 * Improve readability by extracting variable
 * Match change in 2b7d76
This isn't perfect, but it is a best-compromise for GTK's size allocation
This only happens for VERY tall images (limits are large enough
to allow vertical smartphone photos uncropped)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant