To summarize, whatever changes we make, IMO, DPI calculations should meet the following rules for iOS devices:
- "retina" devices should always get the double DPI of their non retina equivalent - "mini" devices should always get the same DPI of their non-mini equivalent. Do you agree with that ? Maurice -----Message d'origine----- De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] Envoyé : jeudi 31 octobre 2013 00:00 À : dev@flex.apache.org Objet : RE: Issue with mobile UI default sizes > On a similar subject do we need to do anyting to support/improve support for > the iPad mini 1st gen (160) or 2nd gen (320)? IMO, Apple and Flex took two different approaches : 1) According to Apple, same app running on iPad mini should look the same that the app running on ipad 2. Which means the UI components will have physical smaller size, but same pixel sizes 2) Flex chose to preserve the physical size, which means that the app will look different on iPad mini and get more pixels. I think we need to follow Apple's approach, which makes me think that iPad 2 and iPad mini needs to get the DPI (=160) Maurice -----Message d'origine----- De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : mercredi 30 octobre 2013 23:13 À : dev@flex.apache.org Objet : Re: Issue with mobile UI default sizes Hi, On a similar subject do we need to do anyting to support/improve support for the iPad mini 1st gen (160) or 2nd gen (320)? We could just "fix" this issue by changing classifyDPI to return 160 rather than 120 for the iPad1 + 2 or perhaps dropping the lower boundary from 140 to 135? (think it 136 right?) Thanks, Justin
