81–90 of 104 posts
I've studied this a great deal, and developed a custom masonry type layout to mitigate the row/column bias. I believe it is a much more balanced layout than the article shows. Using it in Imagist, a paid app. Open to a few beta testers for iOS 7 as well, if you want to judge for yourself.
Side-topic. Shooting Holi [1] without putting your camera in an airtight sealed enclosure is a good way to ruin your equipment. http://en.wikipedia.org/wiki/Holi http://www.lensrentals.com/blog/2013/05/how-to-ruin-your-gea...
Side-topic. Shooting Holi [1] without putting your camera in an airtight sealed enclosure is a good way to ruin your equipment. http://en.wikipedia.org/wiki/Holi http://www.lensrentals.com/blog/2013/05/how-to-ruin-your-gea...
Given that that article says that the supposedly-sealed lenses were also vulnerable, do you have advice on how one would successfully enclose a lens to protect it from the dust?
http://www.bhphotovideo.com/c/product/547694-REG/DiCAPac_WPS...
It like how it looks, but much like Flickr I dislike how it's biased towards landscape pictures. Some of my best photos are portrait, but they get overshadowed by the landscape ones. I imagine the algorithm to cater to both is much harder, because you wouldn't be able to treat each row in isolation, can it actually be solved to a good standard?
This looks like a pretty slick, mobile-compatible photo gallery, but without the code it isn't very useful. They talk about Chromatic like a real product, but "free web service" basically means "demo".
This is why I always preferred vertical masonry. Sites such as VKontakte, Google Image Search, and the recent Flickr app tile things horizontally, but this sometimes means you have to crop the images to fit into your masonry. Not so with vertical masonry, which you can just resize to have constant width.
Vertical masonry doesn't work well to communicate an ordered list of items. Photos are often just that...a story of an experience that happened chronologically. The inability to read left to right on columnar data makes this really hard.
This particular algorithm seems to mix up the order of the photos in order to best fit them on a line, so it can hardly be said to show chronological order.
Since I'm a CS theory person, I can offer some theoretical improvements on the running time and make the problem even more general... Instead of minimize the linear difference of partition, we might want to minimize the standard deviation, or basically any convex function, and still do it in the same time bound. One can reduce this problem to find a k-edge path of minimum weight on a complete DAG. The naive algorithm…