Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>Would it be so bad to treat all xlarge and large screened devices as tablets?</p> </blockquote> <p>If your question really is "is it OK to use the same layouts, etc. for <code>-large</code> and <code>-xlarge</code> devices", that certainly can work. It's certainly where I would start.</p> <p>Bear in mind that device manufacturers really are the ones who determine what is <code>-large</code> or not. It would not surprise me to find some manufacturers creating 5" devices to categorize them as <code>-normal</code>, because they feel that <code>-normal</code> apps tend to work better on their devices than do <code>-large</code> apps.</p> <blockquote> <p>I've noticed that typically, apps I install on my Hannspad use their normal phone UI, with the exception of Evernote which uses a specific tablet interface - I wish I knew how they'd done that.</p> </blockquote> <p>Probably using <code>-large</code>/<code>-xlarge</code> resources. I don't know if they are using fragments or not.</p> <p>In terms of screen sizes, fragments really are for cases where the <code>-large</code>/<code>-xlarge</code> UIs are basically a bunch of <code>-small</code>/<code>-normal</code> sized UIs snapped together like LEGO(R) blocks. In Evernote's case, their <code>-large</code>/<code>-xlarge</code> UI does not fit that pattern, so they may or may not have used fragments.</p> <p>Fragments offer some other advantages for memory management and configuration changes (e.g., screen rotation), so you might consider using fragments even if you are not sharing fragments between major groups of screen sizes.</p> <blockquote> <p>Is that wise?</p> </blockquote> <p>If possible, I would hold off on making that decision until Ice Cream Sandwich ships and we start seeing how some of this stuff will play out on smaller-screen devices.</p>
    singulars
    1. This table or related slice is empty.
    1. POWhat's the best way to support Android 2.x tablets in my app?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USCommonsWare
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhat's the best way to support Android 2.x tablets in my app?
      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
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for the help, I'll use Fragments and treat `large`/`xlarge` devices as tablets. It hadn't occurred to me that manufacturers might deliberately (mis)categorise their 5"-7" devices as `normal` but it makes a lot of sense and hopefully they have done so.
      singulars
      1. PO
      1. USCNorris
 

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