这个应该咋做好？# Programming - 葵花宝典
f*9
1 楼
http://www.appleinsider.com/articles/10/12/11/html5_on_android_samsung_g
alaxy_tab_disappointing_vs_apple_ipad.html
Oversized phone rather than a real tablet
"One of the oddest aspects of the Galaxy Tab browser," Sencha reports,
"is its CSS pixel to device pixel ratio. When queried in landscape mode,
the Galaxy reports a screen.width of 683px and screen.height of 334px.
Since the actual device resolution offers 1024×600, it’s giving us a
1.5× ratio of device to CSS pixels. This is a little bit of an odd
choice since there shouldn’t be any reason why it can’t offer a 1:1
device-to-CSS-pixel ratio (or even just match the iPhone/Nexus One
convention of a 320 pixel device.width — which would give it a 1.875
ratio). This makes the Galaxy slightly bigger than a regular phone
screen in CSS pixels, but not really big enough to handle what people
want to put in a tablet screen."
The firm concluded, "the practical effect of this decision is that the
Galaxy Tab is effectively an 'over-sized phone' for the purposes of web
content. For example, an iPad-style side-navigation section just won’t
fit on the screen. We think it’s probably best to treat it as a phone
with big pixels rather than a true tablet."
One problem with using Android 2.2 for tablets, Sencha explained, was
that "when the Android browser gets ready to animate anything — whether
it’s a CSS animation or a plain old page scroll — it shifts from high-
quality to low-quality display mode. In low-quality mode, it turns off
anti-aliasing (presumably on the theory that since things are moving,
you won’t notice the quality degradation.) This would be less noticeable
on a smaller device. But on the 7″ Galaxy Tab, the resulting pixelation
is striking, particularly since it switches to low-quality mode as soon
as it detects a touch start event (but before anything moves)."
"We’re still waiting for the first awesome Android tablet," the report
observed.
alaxy_tab_disappointing_vs_apple_ipad.html
Oversized phone rather than a real tablet
"One of the oddest aspects of the Galaxy Tab browser," Sencha reports,
"is its CSS pixel to device pixel ratio. When queried in landscape mode,
the Galaxy reports a screen.width of 683px and screen.height of 334px.
Since the actual device resolution offers 1024×600, it’s giving us a
1.5× ratio of device to CSS pixels. This is a little bit of an odd
choice since there shouldn’t be any reason why it can’t offer a 1:1
device-to-CSS-pixel ratio (or even just match the iPhone/Nexus One
convention of a 320 pixel device.width — which would give it a 1.875
ratio). This makes the Galaxy slightly bigger than a regular phone
screen in CSS pixels, but not really big enough to handle what people
want to put in a tablet screen."
The firm concluded, "the practical effect of this decision is that the
Galaxy Tab is effectively an 'over-sized phone' for the purposes of web
content. For example, an iPad-style side-navigation section just won’t
fit on the screen. We think it’s probably best to treat it as a phone
with big pixels rather than a true tablet."
One problem with using Android 2.2 for tablets, Sencha explained, was
that "when the Android browser gets ready to animate anything — whether
it’s a CSS animation or a plain old page scroll — it shifts from high-
quality to low-quality display mode. In low-quality mode, it turns off
anti-aliasing (presumably on the theory that since things are moving,
you won’t notice the quality degradation.) This would be less noticeable
on a smaller device. But on the 7″ Galaxy Tab, the resulting pixelation
is striking, particularly since it switches to low-quality mode as soon
as it detects a touch start event (but before anything moves)."
"We’re still waiting for the first awesome Android tablet," the report
observed.
