On Jul 27, 11:54 pm, Dianne Hackborn <[email protected]> wrote:
> As of today, the platform does not support QVGA devices, so you do not need
> to worry about that. Whenever that situation may be changing, we will give
> advance warning to tell developers how to update to handle such screens, but
> clearly we will also need to do something about all of the existing
> applications that will break on them. Though that something may be to just
> not deliver applications to QVGA devices until they have been updated to say
> that they support such a screen. ;)
>
>
>
>
>
> On Mon, Jul 27, 2009 at 12:58 PM, skink <[email protected]> wrote:
>
> > On Jul 27, 9:13 pm, Dianne Hackborn <[email protected]> wrote:
> > > QVGA is not supported in 1.5, so I wouldn't take any experience you have
> > > running the emulator like that to be a strong evidence of things working
> > how
> > > they would on an actual QVGA device that might appear some time in the
> > > future running something later than 1.5.
>
> > > So you could maybe use it to see if your layouts are behaving reasonably
> > for
> > > different screens, but even for that I would lean towards using an HVGA
> > > density screen that is slightly shorter (like QVGA is slightly shorter
> > than
> > > HVGA) than actually running in QVGA which throws density scaling into the
> > > mix.
>
> > > On Mon, Jul 27, 2009 at 11:00 AM, skink <[email protected]> wrote:
>
> > > > hi,
>
> > > > i have general question about Cupcake (or any other later relase): do
> > > > you, when writing apps, consider running them on qvga device?
>
> > > > although Dianne wrote here
> > > >http://groups.google.com/group/android-developers/msg/73ded3ba1fe7139e
> > > > that qvga is not supported i still see in Cupcake sdk qvga skins...
>
> > > > so my question is: should i really forget about qvga or not?
>
> > > > thanks
> > > > pskink
>
> > > --
> > > Dianne Hackborn
> > > Android framework engineer
> > > [email protected]
>
> > > Note: please don't send private questions to me, as I don't have time to
> > > provide private support, and so won't reply to such e-mails. All such
> > > questions should be posted on public forums, where I and others can see
> > and
> > > answer them.
>
> > thank you Dianne for explanation.
>
> > the problem with qvga is that (as you said) it is normally smaller
> > than hvga and for majority of apps they have to treat qvga differently
> > (eg dialer, calculator)
>
> > if the number of devices with qvga dpy would be for example 0.1% of
> > all android devices then my question is reasonable - does it pay off
> > to make app for non existing case?
>
> > as far i see there was only one device - kogan - with qvga - and it
> > was delayed mainly because of that small display
>
> > thanks
> > pskink
>
> --
> Dianne Hackborn
> Android framework engineer
> [email protected]
>
> Note: please don't send private questions to me, as I don't have time to
> provide private support, and so won't reply to such e-mails. All such
> questions should be posted on public forums, where I and others can see and
> answer them.
thank you Dianne for your exhaustive reply!
pskink
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
