Thanks Alex and Om. I will then make the change. BTW, do you know why the 120 DPI classification was introduced? Is it to match the DENSITY_LOW dpi class on the Android platform?
Maurice -----Message d'origine----- De : omup...@gmail.com [mailto:omup...@gmail.com] De la part de OmPrakash Muppirala Envoyé : vendredi 1 novembre 2013 17:06 À : dev@flex.apache.org Objet : Re: Issue with mobile UI default sizes +1 from me. Thanks, Om On Nov 1, 2013 7:41 AM, "Alex Harui" <aha...@adobe.com> wrote: > I haven't wrestled with this DPI stuff to truly understand the issue, > but I don't see anything obviously wrong with it. > > -Alex > > On 11/1/13 3:32 AM, "Maurice Amsellem" <maurice.amsel...@systar.com> > wrote: > > > > >Hi, I would prefer peer approval on the proposition below before > >going ahead. > >Anyone? > > > >Maurice > > > >________________________________________ > >De : Maurice Amsellem > >Envoyé : jeudi 31 octobre 2013 17:08 > >À : dev@flex.apache.org > >Objet : RE: Issue with mobile UI default sizes > > > >Hi, > > > >Based on yesterday's discussions & suggestions, and putting aside the > >secondary topics for now :-) , this is what could be done and why : > > > >Requirements to be compliant with Apple's specs on iOS devices: > >1) "retina" devices should always get the double DPI of their non > >retina equivalent > >2) "mini" devices should always get the same DPI of their non-mini > >equivalent. > > > >To meet the above requirements, these are the DPI classifications for > >iOS > >devices: > >iPad 1+2 => 160 DPI (real:132) > >iPad 3+4 => 320 DPI (real: 264) > >iPad mini 1 => 160 DPI (real:163) > >iPad mini retina => 320 DPI (real:326) > > > >This is basically equivalent to reverting back to SDK 4.10 DPI > >classification , and fix the common issue with iPad 3+4. > > > >The change should be done in the default RuntimeDPIProvider, and > >specifically for the devices above , so as not to impact other devices... > > > >What do you think ? > > > >Maurice > > > >PS: > >Actually there are two other possibilities that also meet the > >requirement and that I rejected: > >2) use the 120 / 240 instead of 160 / 320 for all iOS devices that is > >SDK 4.11 extended to "mini", => but then people are complaining that > >the UI is too small (smaller than what it used to be) > > > >3) use 120 / 240 for all iOS devices, AND scale up all CSS and AS > >Script by 1.33 => far too costly.. > > > > > >-----Message d'origine----- > >De : Maurice Amsellem [mailto:maurice.amsel...@systar.com] > >Envoyé : jeudi 31 octobre 2013 01:02 > >À : dev@flex.apache.org > >Objet : RE: Issue with mobile UI default sizes > > > >I can confirm these figures for SDK 4.10 > > > >- iPad 1+2 = 160 dpi (real: 132) > >- iPad 3+4 = 240 dpi (real: 263) > >- iPad mini 1 = 160 dpi (real: 163). > > > >And for SDK 4.11: > >- iPad 1+2 = 120 dpi (real: 132) > >- iPad 3 = 240 dpi (real: 263) > > > >So if the buckets didn't change in SDK 4.11, I guess that your > >figures for iPad mini 1 and 2 are correct for SDK 4.11 > > > >Maurice > > > >-----Message d'origine----- > >De : Justin Mclean [mailto:jus...@classsoftware.com] Envoyé : jeudi > >31 octobre 2013 00:40 À : dev@flex.apache.org Objet : Re: Issue with > >mobile UI default sizes > > > >Hi, > > > >Currently this is what classifyDPI returns: > >- iPad1+2 = 120 dpi > >- iPad 3+4+Air = 240 dpi > >- iPad min 1 = 160 dpi > >- iPad mini 2 = 320 dpi > > > >Or so I assueme form the specs anyone confirm on a real device? > > > >Thanks, > >Justin > >
