Bug 3225 – Ugly/slow resized application images

Bug 3225 - Ugly/slow resized application images


Summary:	Ugly/slow resized application images

Status:	RESOLVED FIXED

Product:	maemo.org Website
Component:	Downloads
Version:	unspecified
Platform:	All All

Importance:	Medium enhancement (vote)
Target Milestone:	---
Assigned To:	Niels Breet
QA Contact:	downloads@maemo.org

URL:	http://maemo.org/downloads/OS2008/
Keywords:	performance

Depends on:
Blocks:
	Show dependency tree

Reported:	2008-06-05 22:11 UTC by Eugene
Modified:	2008-07-08 18:41 UTC (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note

You need to log in before you can comment on or make changes to this bug.

Description Eugene (reporter) 2008-06-05 22:11:39 UTC

When clicking on any application image the bigger image that appears is a bit
ugly - it seems to be resized to 540x324 using very simple and very rough
utility. The workaround is to upload already resized images converted by
Gimp(as I do) or do it on server automatically by more sophisticated tool. May
be ImageMagick?

To see the difference, compare some random apps with text:
http://maemo.org/downloads/product/OS2008/zapys/
http://maemo.org/downloads/product/OS2008/vagalume/

with my uploaded images for Stardict or Labyrinth -
http://maemo.org/downloads/product/OS2008/stardict/
http://maemo.org/downloads/product/OS2008/labyrinth/

It's not a big deal but average user may think of the application as of
something ugly way before he downloads it :)

Comment 1 Niels Breet maemo.org

2008-06-06 12:43:49 UTC

What you see is the browser itself resizing the image because we set a size
constraint in the image tag. This is the ugly and lazy way of resizing.

If you use FF3, you will see it already looks a lot better because this browser
does better resizing.

We obviously need to do the resizing ourselves. So I will keep this as an
enhancement request.

Comment 2 Eero Tamminen nokia

2008-06-12 17:25:53 UTC

(In reply to comment #1)
> What you see is the browser itself resizing the image because we set a size
> constraint in the image tag. This is the ugly and lazy way of resizing.

This also slows down the page loading and uses more memory from the device
browser.  I.e. it's not just the ugly looks that gives a bad impression
of the maemo software.  I'd put more priority on this, our own pages
should be optimized to make the devices look good, not the other way
round.

Comment 3 Niels Breet maemo.org

2008-07-08 18:41:11 UTC

I have added the following:

All bigger images are now 400px wide. This is their native size. We resize
images to be 400px wide on upload.

The old code used the original image, which could be bigger than 400px.

The new code doesn't force the size anymore, so browser based scaling should be
a thing of the past. No more memory and cpu power wasting for screenshots.