blackberry playbook - 7in tablets in Android - screen size qualifiers -


i encountered weird behaviour when starting test app on 7in android models , find out if others finding same problem , people recommend fix.

here details:

the application has full tablet support, triggered qualifiers layouts. xlarge devices tablet mode multiple fragments being displayed on screen.

for newer android versions there values set variable change ui on flow using sw600dp qualifier xlarge one.

the problem:

i testing on kindle fire , rim blackberry playbook , want support upcoming google nexus tablet (or whatever called) , other 7in form factor devices.

both playbook fire have 7in screen , 1024x600 screen resolution.

however playbook seems trick android thinking xlarge device, while fire not that.

both tablet standard ui work fine, imho tablet mode nicer , fine used on 7in device. if push layout large qualifier tablet mode on fire e.g. on note or other quite bit smaller devices.

with android 4x can use sw600dp , other qualifiers older versions? assume 7in device supposed behave tablet e.g. note..

what best practices scenario? observations playbook reporting xlarge correct?

however playbook seems trick android thinking xlarge device, while fire not that.

device manufacturers ones choose buckets device goes in respect size , density. goes double manufacturers rim , amazon, not want play store , therefore not have abide particular compatibility requirements play store dictates, welcome thumb noses @ google's guidance.

what best practices scenario?

i can't tell "best".

however, if there specific devices wish override layouts use specific size, here's try (assuming layout using normal cases known r.layout.main):

step #1: create res/layout/main_funky.xml symlink or hardlink res/layout-xlarge/main.xml (and likewise -land, etc.).

step #2: in java code, wherever refer r.layout.main (e.g., oncreateview() of fragment), decide whether load r.layout.main or r.layout.main_funky depending upon android.os.build data detect these oddball devices model. since r.layout.main_funky 1 of normal main layouts, of code depends upon widgets should unaffected choice.

step #3: in particular case, add mmpd (magic maven pixie dust) steps #1 , #2... :-)

are observations playbook reporting xlarge correct?

i bought playbook, determined rim's distribution model is... unpleasant, , did bare minimum have book chapter on it. haven't tried see if -large, -xlarge, or else.

that being said, nook tablet iirc suffers (claiming -xlarge rather -large).

i expect google nexus tablet, if such thing comes fruition, correctly honor size buckets, plus running new enough android version -sw600dp , kin work.


Comments

Popular posts from this blog

java - Play! framework 2.0: How to display multiple image? -

gmail - Is there any documentation for read-only access to the Google Contacts API? -

php - Controller/JToolBar not working in Joomla 2.5 -