Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>A workaround for api level 10 could be something like this:</p> <ol> <li><p>use the compat lib from the SDK so that you can design with fragments.</p></li> <li><p>Assume everything before android 3 is a phone. For example use your layout files in layout/* for this (and the rest will be based it on unless overriden). This assumption is basically only wrong for the original Samsung Galaxy Tab 7" from 2009.</p></li> <li><p>Assume everything on android 3.x is a tablet (they are), so do some tablet specific layout if you want and have them under layout-v11 (and maybe also layout-v12 if there is anything specific to android 3.1). Tablet specific layout could mean that you arrange your fragments differently and/or show multiple fragments at the same time.</p></li> <li><p>Everything newer (android 3.2+) you can use the new stuff from api level 13. Such as layout-sw600dp/ for some layouts etc etc. <a href="http://developer.android.com/guide/practices/screens_support.html#DeclaringTabletLayouts" rel="nofollow">http://developer.android.com/guide/practices/screens_support.html#DeclaringTabletLayouts</a></p></li> </ol>
    singulars
    1. This table or related slice is empty.
    1. POScreen resolution / Physical size
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMattias Isegran Bergander
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POScreen resolution / Physical size
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. CO(Copied from another thread): Good idea, but does it mean creating two applications at a time. In specification actually it is said that app should handle following resolutions, including 1280x800, yet why you think there's no possibility to handle that sort of thing in 10th API ? For instance here developer.android.com/guide/practices/screens_support.html layout-xlarge it is supposed to handle "Extra Large screen" devices(at the bottom). "Extra Large screen" means tablet as well - isn't it ?
      singulars
      1. PO
      1. This table or related slice is empty.
    2. COWell depends a bit but generally yes. Go ahead, the emulator can show you how it works in practice. But remember we now have 1280x720 resolution on phones as well. The graphic here with both dpi and screen sizes can perhaps help you visualise it: http://developer.android.com/guide/practices/screens_support.html#range But you could use layout-xlarge-land as well, had forgotten about landscape mode too, you could/(should probably) design differently for that as well.
      singulars
      1. PO
      1. USMattias Isegran Bergander
    3. COThank you for suggestions, I'll continue researching this issue. But one more question, if you don't mind. In "multiple screens" article it is that if one would like to create a custom avd he can do so. One thing I can't figure out is setting physical size. AFAIK physical sizes are measured in inches and in case of predefined emulators QWGA,HVGA size is somehow defined automatically. But how do I specify physical size when I build a custom AVD ?
      singulars
      1. PO
      1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

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