Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The <code>GridLayout</code> as suggested by someone else is not flexible enough to do this. To do this, use the <code>android:layout_weight</code> property. This allows you to fill the available space according to the fractions specified.</p> <p><strong>Example with the equal weights:</strong></p> <pre><code>&lt;LinearLayout android:layout_width="match_parent" android:layout_height="100dp"&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="A" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="B" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="C" /&gt; &lt;/LinearLayout&gt; </code></pre> <p><img src="https://i.imgur.com/1ITp8XY.png" /></p> <p><strong>Example with different weights:</strong></p> <pre><code>&lt;LinearLayout android:layout_width="match_parent" android:layout_height="100dp"&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="A" /&gt; &lt;Button android:layout_weight="2" android:layout_width="match_parent" android:layout_height="match_parent" android:text="B" /&gt; &lt;Button android:layout_weight="2" android:layout_width="match_parent" android:layout_height="match_parent" android:text="C" /&gt; &lt;/LinearLayout&gt; </code></pre> <p><img src="https://i.imgur.com/cJ5AhHp.png" /></p> <p><strong>More complex example</strong></p> <p>Here is a more complex example for a layout like used in a calculator app that uses multiple <code>LinearLayout</code>s:</p> <pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt; &lt;LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent" android:orientation="vertical"&gt; &lt;LinearLayout android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent"&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="7" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="8" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="9" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="x" /&gt; &lt;/LinearLayout&gt; &lt;LinearLayout android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent"&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="4" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="5" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="6" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="-" /&gt; &lt;/LinearLayout&gt; &lt;LinearLayout android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent"&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="1" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="2" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="3" /&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="+" /&gt; &lt;/LinearLayout&gt; &lt;LinearLayout android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent"&gt; &lt;Button android:layout_weight="1" android:layout_width="match_parent" android:layout_height="match_parent" android:text="0" /&gt; &lt;Button android:layout_weight="1.5" android:layout_width="match_parent" android:layout_height="match_parent" android:text="." /&gt; &lt;Button android:layout_weight="1.5" android:layout_width="match_parent" android:layout_height="match_parent" android:text="=" /&gt; &lt;/LinearLayout&gt; &lt;/LinearLayout&gt; </code></pre> <p><img src="https://i.imgur.com/dx0q8U1.png" /></p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid - How do you scale views to fit a full screen application's height and width perfectly?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USOverv
    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.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COSee my 2nd point: "Nesting LinearLayouts with Layout weights. This works, but lint gives performance warnings because I am nesting weights. On top of that, it does not take into account text size. So on small screens, text is chopped off. Conversely, on large screens, text is too small." This is currently my best solution too, but as you can see from your screenshot, the text does not scale along with the view
      singulars
      1. PO
      1. USBradley Campbell
    2. CO@grandstaish Don't worry about the performance. I use it in my app and it works fine on low-end devices as well. You can make the text scale properly by using different layouts for different screen sizes. It won't be automatic, but it's as close as you'll get non-programmatically.
      singulars
      1. PO
      1. USOverv
    3. COTrue. You wouldn't even need extra layouts, you would just use different styles for different screen sizes (i.e. define a different textSize in each style directory). This is looking like the best solution. I will mark it as an answer tomorrow unless anyone else comes up with something
      singulars
      1. PO
      1. USBradley Campbell
 

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