Given the recent announcement by Kogan is it worth putting effort into
trying to support QVGA?
From the -developers list it sounds like very few apps will have a
usable UI in QVGA, so maybe it should be dropped as an option?
Al.
Jean-Baptiste Queru wrote:
That all sounds good, thanks.
Two points:
-Android 1.0, which is the one that Kogan must have been using, didn't
support QVGA in its built-in-apps nor did it have framework support to
help 3rd-party apps adapt to different densities. Fixing that is on
the roadmap.
-As for 3rd-party apps, it's potentially a chicken-and-egg
Hi Mathias:
Just interested to know, what's the relationship between surfaceflinger
and pixelflinger?
Meanwhile, is there some document on sufraceflinger and pixelflinger?
Thanks.
--
Chen
On Sat, Jan 17, 2009 at 5:58 AM, Mathias Agopian pixelflin...@google.comwrote:
On Fri, Jan 16,
It's easy to allow HVGA apps to run on things with a resolution greater
than HVGA, but trying to down-scale any HVGA system to QVGA usually ends
up with mangled icons, unreadable text, and problems with layouts, so
I'd suggest unless it's a next to zero cost thing in terms of time
and/or
I've a similar problem that does not seem to be related to any missing
tool/compiler/parser in Ubuntu 8.10. Though the Ubuntu 8.10 default
gcc is 4.3.2, but I have 'apt-get install gcc-4.2'
$ TARGET_ARCH=x86 TARGET_PRODUCT=eee_701 DISABLE_DEXPREOPT=true
CC=gcc-4.2 CXX=g++-4.2 make -j2
Thanks for clarifying, Dianne.
On Jan 16, 4:41 pm, Dianne Hackborn hack...@android.com wrote:
I'd like to qualify that a little -- this work is to introduce support for
different densities in the system, targeting only QVGA and WVGA screens that
are approximately the same physical size as the
SurfaceFlinger is the surface compositor and PixelFlinger is the
blitter.
On Jan 17, 5:08 am, Chen Yang sunsety...@gmail.com wrote:
Hi Mathias:
Just interested to know, what's the relationship between surfaceflinger
and pixelflinger?
Meanwhile, is there some document on
On Sat, Jan 17, 2009 at 1:23 AM, Al Sutton a...@funkyandroid.com wrote:
Given the recent announcement by Kogan is it worth putting effort into
trying to support QVGA?
The work isn't being done for Kogan, so there is no reason for them to
impact it.
From the -developers list it sounds like
