maemo.org - Talk - View Single Post - The Epic Android Thread

	Capt'n Corrupt	2010-11-21 , 20:27
	Posts: 3,524 \| Thanked: 2,958 times \| Joined on Oct 2007 @ Delta Quadrant	#1220

Originally Posted by SD69

Umm, the document says the opposite of resolution independent -

"To simplify ... user interfaces ..., the platform divides the range of actual supported screen sizes and resolutions into: a set of three..."

"The objective of supporting multiple screens is to create an application that can run properly on any display and function properly on any of the generalized screen configurations supported by the platform."

But this is the essence of resolution independence. Instead of hard pixels, they use 'dips' and instead of screen resolution, the UI uses three generalized screen sizes and three generalized densities. Even the UI widgets are designed to flow/stretch to fit different screen dimensions.

The 'screen sizes' are not hard-coded values but rather 'loose' definitions of small screens (think tiny PMPs), medium screens (think smartphones), and large screens (think tablets). Additionally, the pixel density is accounted for with three generalized denominations.

Originally Posted by SD69

I recognize that 800x480 is not the only resolution supported by Android, but it is the only one even remotely suitable for a 7" tablet.

This is not the situation with Maemo (or vanilla GTK+) AFAIK.

You'll have to explain this point as it doesn't make sense to me. This implies that the Galaxy Tab's 1024x600 resolution isn't suitable for it's screen size. How does Maemo tackle this issue?

Just to follow up:

It's worth looking at this discussion on the Tab and Android's UI:
http://groups.google.com/group/andro...ad1666dacb3647

See my previous post. There is no compatibility issue with running the UI at a higher density than the normal bucket for its actual density. It just means you want to have a larger UI for the user.

The big thing we don't want to have happen here is for developers to have to tweak their UI to account for this. You should *not* do that. Let the manufacturer do this, and if it results in an absurdly large UI for apps, well that is what the made for their device. (In this case I believe it is fine.)

That was written by an Android framework engineer. This is VERY good solution to the multi-res/multi-size problem.

Last edited by Capt'n Corrupt; 2010-11-21 at 21:02.

Quote & Reply |

The Following User Says Thank You to Capt'n Corrupt For This Useful Post:
danramos