This prevents portrait photos from being assigned a cropped landscape slot in the mosaic, at the cost of the ordering being less chronological. Merge at your own discretion.
This reverts commit 0d1fce41c8e7173f3ef6cad3ab72bb5e4ab29953.
This prevents portrait photos from being assigned a cropped landscape slot in the mosaic, at the cost of the ordering being less chronological. Merge at your own discretion.
Fixes #9.
This reverts commit 0d1fce41c8.
This prevents portrait photos from being assigned a cropped landscape
slot in the mosaic, at the cost of the ordering being less
chronological.
I agree the original solution isn't the best, and really more of a workaround. However, I think reverting it isn't the right solution, either — for the same reason you've already mentioned. I expect it to lead to very confusing back/forward behaviour in the viewer.
Ideally, we'd change the initial heuristic outright. Instead of basing the content on the layout, it should really be the other way around. Yes, doing so will require more of a patch, but I think it's worth investing some time in that.
I agree the original solution isn't the best, and really more of a workaround. However, I think reverting it isn't the right solution, either — for the same reason you've already mentioned. I expect it to lead to very confusing back/forward behaviour in the viewer.
Ideally, we'd change the initial heuristic outright. Instead of basing the content on the layout, it should really be the other way around. Yes, doing so will require more of a patch, but I think it's worth investing some time in that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This reverts commit
0d1fce41c8.This prevents portrait photos from being assigned a cropped landscape slot in the mosaic, at the cost of the ordering being less chronological. Merge at your own discretion.
Fixes #9.
I agree the original solution isn't the best, and really more of a workaround. However, I think reverting it isn't the right solution, either — for the same reason you've already mentioned. I expect it to lead to very confusing back/forward behaviour in the viewer.
Ideally, we'd change the initial heuristic outright. Instead of basing the content on the layout, it should really be the other way around. Yes, doing so will require more of a patch, but I think it's worth investing some time in that.
All right, I'll close this :)
Pull request closed