search

cyclestreets / mobileweb2011

Mobile HTML client - LEGACY site
https://oldm.cyclestreets.net/
13 stars 2 forks source link

Small Photos on /location/#nnn #45

Open si-the-pie opened 12 years ago

si-the-pie commented 12 years ago

Shaun writes 16 Jun that: 66 I find that on the mobile photo map pages the photo is so low resolution that it is impossible to read what is in them. 99

http://lists.cyclestreets.net/mailman/private/mobile/2012-June/000625.html

and provides a screen snapshot.

si-the-pie commented 12 years ago

When viewing:

http://m.cyclestreets.net/location/#39396

on a small screen such as HTC Wildfire the image requested is:

/location/39396/cyclestreets39396-size250.jpg

and the same page viewed on a Blackberry Playbook with a bigger screen is:

/location/39396/cyclestreets39396-size640.jpg

ditto via a large screen laptop.

smsm1 commented 11 years ago

On the Samsung Galaxy S3 there is blocky unclear image.

si-the-pie commented 11 years ago

Latest update adds a click from the thumbnail on pages like http://m.cyclestreets.net/location/#39396 directly to the photo so that you can zoom in.

In pages of the form: /location/#nnnn there is CSS on the tag that has width=100% which explains why the thumbnail stays the size it is while zooming in or out. The maplets zoom but the photo stays as it is - quite frustrating.

I've also found that photos are also displayed using /photomap/ url - by different code (possibly as a popup?) - which has yet to be updated to this latest change.

mvl22 commented 11 years ago

The solution is surely just to increase from 640px (or whatever it is) to 1024px, after which the same fit-to-width will be applied by the browser. It won't be that much larger a file, and these days that seems more sensible given mobile screen improvements over the last 2 years.

si-the-pie commented 11 years ago

I think the issue was the because of the tag width=100% the mobile device was requesting only very small thumbnails. My link through to a 640px image was a very simple change. A fuller solution could include changing the css, and also the cyclestreets api to provide larger images - I avoided getting to involved in that as there are heaps of other changes going on at the moment.

Also I think there's merit in completely changing the way photos are handled in the app, so I don't think its worth spending too much resource on this.