Note that there are some explanatory texts on larger screens.

plurals
  1. POAndroid Different Resolution Support in IBM Worklight
    primarykey
    data
    text
    <p>I am searching on different resolution support in IBM Worklight android . From this side i am reading tutorials <a href="http://www.ibm.com/developerworks/mobile/worklight/getting-started.html#mobile-client-development" rel="nofollow">IBM Worklight Tutorials</a> In tutorial/module 09 they discuss about different resolutions. In the document there is line which telling:</p> <blockquote> <p>By default, Android application assumes that the application HTML file was styled for a screen width of 320 pixels. When displaying graphical elements on wider screens, Android automatically scales images and fonts to the appropriate ratio. For example, on a 480-pixel wide screen, a 100-pixel wide image will be scaled by 480/320 (= 1.5) to 150 pixels in width</p> </blockquote> <p>Now i make a Worklight Hybrid project and set a background image in it and two buttons on this image. Its a demo app in which i am testing different resolutions. </p> <p>Now i deploy this app in android and run it on Tab 7 inch ,nexus 4 and tab 10.1 .Now my image size is 580x320 and bit depth is 24. </p> <p>When i run this project on nexus 4 it gives the width of image correct but it do not scales the image height vise.</p> <p>When i run this project on tab 7 2 , it shows the image having some extra white space on the left of image and extra white space on height of image means down the image. </p> <p>When i run on tab 10.1 it shows the same behavior as the tab 7 2 did. </p> <p>I am really confuse that which exact general size will be use so that all these scale on all screen sizes and not shows extra white space on width and on height</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload