yeah i did, but it wasn't much help, perhaps I didn't understand what you were saying --
"Just scale your coordinates based on the screen density." That is what I was commenting on. Screen density does not seem sufficient to me. "You can't assume some specific size for some screen -- consider the possibilities, QVGA, HVGA, WVGA, FWVGA all have different proportions." by "specific size" - i assume you meant physical screen size -- which goes back to density. as far as "different proportions" I assume you mean "aspect ratio". I'm not quite sure what that means. Does that mean I should create a separate graphic for each screen DENSITY and then it looks however it looks on whatever the aspect ratio is for a screen? Suppose I had two devices A and B with the same screen DENSITY. Device A had an aspect ratio such that it was 2x as wide as device B (but again, with the same screen density). If I create an app widget for device A to be 4x1 (to take up the entire width of the screen), then when I used that widget graphic on device B (with the same density, but 2x physical width), the widget graphic would only go across half the screen? On Nov 1, 1:23 pm, Dianne Hackborn <hack...@android.com> wrote: > Did you read my second paragraph? > > > > On Sun, Nov 1, 2009 at 10:57 AM, sdphil <phil.pellouch...@gmail.com> wrote: > > It seems that screen density alone is not sufficient to know what the > > dimension should be; at some point "aspect ratio" has to come into > > play. For example, I could have a screen that is the same screen > > "density" as a T-Mobile G1, but twice has tall (physical screen size; > > and 2x as many pixels in that direction). the 4x1 widget dimensions > > in portrait would be fine as is, but when I went to landscape, the > > width of my app widget would have to be much greater than 424 pixels > > even though the screen "density" was the same. > > > and that's what is kind of happening with T-Mobile G1 and Motorola > > Droid (at least it seems that way). > > > T-Mobile G1: 181dpi, aspect ratio in landscape is: 480/320 = 1.5 > > Motorola Droid: 267dpi, aspect ratio in landscape is: 854/480 = 1.78 > > > If I just scaled everything up based on screen density, then Droid > > should be: 267/181 = 1.475 scale factor. > > > If the aspect ratio of the phones were exactly the same, then i would > > agree, you could just use the screen density scale factor. But the > > aspect ratios are not the same. > > > On Nov 1, 8:51 am, Dianne Hackborn <hack...@android.com> wrote: > > > Please read on screen density: > > > >http://developer.android.com/guide/practices/screens_support.html > > > > <http://developer.android.com/guide/practices/screens_support.html>Just > > > scale your coordinates based on the screen density. You can't assume > > some > > > specific size for some screen -- consider the possibilities, QVGA, HVGA, > > > WVGA, FWVGA all have different proportions. And then a particular app > > may > > > use the screen differently, for example in the future home will probably > > > have some redesign so that on a FWVGA screen there is not such a > > difference > > > in proportion between its landscape and portrait layouts. > > > > On Sun, Nov 1, 2009 at 7:40 AM, sdphil <phil.pellouch...@gmail.com> > > wrote: > > > > not sure I follow you here -- > > > > > T-Mobile G1/G2 has the following specs - > > > > 320px x 480px (pixels) > > > > 1.77" x 2.65" (inches) > > > > which gives about 181 dpi. > > > > > according to this -- > > > > >http://developer.android.com/guide/practices/ui_guidelines/widget_des. > > .. > > > > > 4x1 widgets on T-Mobile G1 and G2 should be 320x100 in portrait > > > > and 424x74 in landscape. > > > > > Motorola Droid has the following specs - > > > > 480px x 854px (pixels) > > > > 1.8" x 3.2" (inches) > > > > which gives about 267 dpi. > > > > > 4x1 widgets for both portrait and landscape on something like Droid > > > > should be what? > > > > > According to what you said "Multiply by 1.5" > > > > > 320*1.5 x 100*1.5 = 480 x 150 portrait > > > > 424*1.5 x 74*1.5 = 636 x 111 landscape > > > > > I can believe it for portrait, but for landscape, that doesn't seem > > > > right. > > > > > tia. > > > > > On Oct 31, 3:11 pm, Dianne Hackborn <hack...@android.com> wrote: > > > > > It's not the number of pixels, it's the density. > > > > > > On Sat, Oct 31, 2009 at 12:10 PM, sdphil <phil.pellouch...@gmail.com > > > > > wrote: > > > > > > That makes sense for portrait (480 / 320 = 1.5) but for fwvga in > > > > > > landscape, 854 / 480 = 1.78. > > > > > > > On Oct 31, 10:55 am, Dianne Hackborn <hack...@android.com> wrote: > > > > > > > Multiply by 1.5. > > > > > > > > On Sat, Oct 31, 2009 at 8:23 AM, sdphil < > > phil.pellouch...@gmail.com> > > > > > > wrote: > > > > > > > > what are the 4x1 app widget sizes for WVGA and FWVGA in both > > > > portrait > > > > > > > > and landscape? > > > > > > > > > -- > > > > > > > > You received this message because you are subscribed to the > > Google > > > > > > > > Groups "Android Developers" group. > > > > > > > > To post to this group, send email to > > > > > > android-developers@googlegroups.com > > > > > > > > To unsubscribe from this group, send email to > > > > > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > > > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > <android-developers%252bunsubscr...@googlegroups.com<android-developers%25252bunsubscr...@googlegroups.com> > > > > > ><android-developers%2Bunsubs > > > > > > cr...@googlegroups.com> > > > > > > > > For more options, visit this group at > > > > > > > >http://groups.google.com/group/android-developers?hl=en > > > > > > > > -- > > > > > > > Dianne Hackborn > > > > > > > Android framework engineer > > > > > > > hack...@android.com > > > > > > > > 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. > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google > > > > > > Groups "Android Developers" group. > > > > > > To post to this group, send email to > > > > android-developers@googlegroups.com > > > > > > To unsubscribe from this group, send email to > > > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > > > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > <android-developers%252bunsubscr...@googlegroups.com<android-developers%25252bunsubscr...@googlegroups.com> > > > > > > > For more options, visit this group at > > > > > >http://groups.google.com/group/android-developers?hl=en > > > > > > -- > > > > > Dianne Hackborn > > > > > Android framework engineer > > > > > hack...@android.com > > > > > > 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. > > > > > -- > > > > You received this message because you are subscribed to the Google > > > > Groups "Android Developers" group. > > > > To post to this group, send email to > > android-developers@googlegroups.com > > > > To unsubscribe from this group, send email to > > > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > > <android-developers%2bunsubscr...@googlegroups.com<android-developers%252bunsubscr...@googlegroups.com> > > > > > For more options, visit this group at > > > >http://groups.google.com/group/android-developers?hl=en > > > > -- > > > Dianne Hackborn > > > Android framework engineer > > > hack...@android.com > > > > 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. > > > -- > > You received this message because you are subscribed to the Google > > Groups "Android Developers" group. > > To post to this group, send email to android-developers@googlegroups.com > > To unsubscribe from this group, send email to > > android-developers+unsubscr...@googlegroups.com<android-developers%2bunsubscr...@googlegroups.com> > > For more options, visit this group at > >http://groups.google.com/group/android-developers?hl=en > > -- > Dianne Hackborn > Android framework engineer > hack...@android.com > > 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. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
