On Feb 7, 2014, at 7:35 AM, Vincent van Ravesteijn <v...@lyx.org> wrote:
> On Fri, Feb 7, 2014 at 4:31 AM, Andrew Keller <and...@kellerfarm.com> wrote: >> I recently used Git to archive a set of scanned photos, and I used gitweb to >> provide access to them. Overall, everything worked well, but I found it >> undesirable that I had to zoom out in my browser on every photo to see the >> whole photo. In the spirit of making the default behavior the most likely >> correct behavior, this patch seems to be a good idea. >> >> However, I'm not an expert on the use cases of gitweb. In order for the >> maximum size constraints to take effect, the image would have to be at least >> the size of the web browser window (minus a handful of pixels), so the >> affected images are usually going to be pretty big. Are there any common >> use cases for displaying a large image without scaling (and hence, with >> scrolling)? >> >> Thanks, >> Andrew >> > > It sounds like your usecase is exactly what camlistore.org tries to achieve. Yes. With that said, I don't think it's unreasonable for a software project to contain images larger than a browser window. And, when that happens, I'm pretty confident that the default behavior should be to scale the image down so the user can see the whole thing. - Andrew -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
