Great, Your first answer also covered my second question!
Do you intend to do this work in cupcake or donut or ...? If an application is designed to run on a larger device; say it only had VGA resources, would you just reject installing it on a smaller screen device such as HVGA or QVGA or are you planning to support this downscaling path as well? Thanks again, Jason. On Apr 1, 10:59 am, Romain Guy <[email protected]> wrote: > Hi, > > What's missing is mostly the compatibility layer. Applications will > not all work at various resolutions. These applications will need to > be rendered in a specific way, probably by scaling the entire view > hierarchy and translating touch events (the app will think it's > running in h...@160density.) > > > I am also interested > > to know if you have plans to improve the application UI framework > > further for different screen sizes > > What exactly do you mean? The UI framework can already work at various > resolutions and densities. It's up to the app to use it correctly :) > > -- > Romain Guy > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time > to provide private support. All such questions should be posted on > public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" 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-framework?hl=en -~----------~----~----~----~------~----~------~--~---
