Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You probably should just manually add your items to <code>LinearLayout</code>:</p> <pre><code>LinearLayout layout = ... // Your linear layout. ListAdapter adapter = ... // Your adapter. final int adapterCount = adapter.getCount(); for (int i = 0; i &lt; adapterCount; i++) { View item = adapter.getView(i, null, null); layout.addView(item); } </code></pre> <p><strong>EDIT</strong>: I rejected this approach when I needed to display about 200 non-trivial list items, it is very slow - Nexus 4 needed about 2 seconds to display my "list", that was unacceptable. So I turned to Flo's approach with headers. It works much faster because list views are created on demand when user scrolls, not at the time the view is created.</p> <p><strong>Resume:</strong> The manual addition of views to layout is easier to code (thus potentially less moving parts and bugs), but suffers from performance problems, so if you have like 50 views or more, I advise to use the header approach.</p> <p>Example. Basically the activity (or fragment) layout transforms to something like this (no ScrollView needed anymore):</p> <pre><code>&lt;ListView xmlns:android="http://schemas.android.com/apk/res/android" android:id="@+id/my_top_layout" android:layout_width="fill_parent" android:layout_height="fill_parent"/&gt; </code></pre> <p>Then in <code>onCreateView()</code> (I'll use an example with a fragment) you need to add a header view and then set an adapter (I assume the header resource ID is <code>header_layout</code>):</p> <pre><code>ListView listView = (ListView) inflater.inflate(R.layout.my_top_layout, container, false); View header = inflater.inflate(R.layout.header_layout, null); // Initialize your header here. listView.addHeaderView(header, null, false); BaseAdapter adapter = // ... Initialize your adapter. listView.setAdapter(adapter); // Just as a bonus - if you want to do something with your list items: view.setOnItemClickListener(new AdapterView.OnItemClickListener() { @Override public void onItemClick(AdapterView&lt;?&gt; parent, View view, int position, long id) { // You can just use listView instead of parent casted to ListView. if (position &gt;= ((ListView) parent).getHeaderViewsCount()) { // Note the usage of getItemAtPosition() instead of adapter's getItem() because // the latter does not take into account the header (which has position 0). Object obj = parent.getItemAtPosition(position); // Do something with your object. } } }); </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUsing a ListAdapter to fill a LinearLayout inside a ScrollView layout
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USsmok
    1. USsmok
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POUsing a ListAdapter to fill a LinearLayout inside a ScrollView layout
      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. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYes, that was the second idea I had but i wasn't sure of the `ListAdapter` and the `ListView` does more magic behind the screens which I then don't do manually.
      singulars
      1. PO
      1. USStefan Hoth
    2. COOf course ListView does some magic, at least dividers between elements, you would have to add them manually, I guess. ListAdapter (if it is implemented correctly) should not do any more magic.
      singulars
      1. PO
      1. USsmok
    3. COI went with this solution as it fits my purpose better (bigger layout, small list). If it would be the other way around I'd go with the solution provided by Flo as it allows reusage of elements in the `ListView` for better performance.
      singulars
      1. PO
      1. USStefan Hoth
 

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