Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>It's certainly possible, the only thing you need to do is to generate your own IDs. The IDs may be anything but they must not conflict with the aapt IDs (the ones in R) and must not be negative.</p> <p>The following example demonstrates this with a set of fixed IDs:</p> <pre><code>public class MainActivity extends Activity { private final int ID_TABLE = 0xA; private final int ID_ROW1 = 0xB; private final int ID_ROW2 = 0xC; @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); LinearLayout ll = (LinearLayout) findViewById(R.id.root); TableLayout tl = new TableLayout(this); tl.setId(ID_TABLE); TableRow tr1 = new TableRow(this); tr1.setId(ID_ROW1); TableRow tr2 = new TableRow(this); tr2.setId(ID_ROW2); tl.addView(tr1); tl.addView(tr2); ll.addView(tl); MyFragment frag1 = new MyFragment(); MyFragment frag2 = new MyFragment(); MyFragment frag3 = new MyFragment(); MyFragment frag4 = new MyFragment(); getFragmentManager().beginTransaction() .add(ID_ROW1, frag1, "cell1_1") .add(ID_ROW1, frag2, "cell1_2") .add(ID_ROW2, frag3, "cell2_1") .add(ID_ROW2, frag4, "cell2_2") .commit(); getFragmentManager().executePendingTransactions(); } } </code></pre> <p>In order to switch to a different layout, you can remove the fragments and add them elsewhere.<br> Let me know how it goes.</p> <p>EDIT: to clarify, Views and ViewGroups don't need to be instantiated once and then kept for the lifetime of the Activity. Just make sure any fragments are either removed or detached before removing their associated view. Also, if you create and remove views outside of onCreate you should make sure it can be restored by using onSaveInstanceState and repeating the process in onCreate. Read the <a href="http://d.android.com/reference/android/app/Activity.html" rel="nofollow">diagram here</a> and the paragraph about <a href="http://developer.android.com/reference/android/app/Activity.html#ConfigurationChanges" rel="nofollow">configuration changes</a>.</p>
    singulars
    1. This table or related slice is empty.
    1. POAndroid - Change fragment layout in runtime
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USuser999717
    1. USuser999717
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POAndroid - Change fragment layout in runtime
      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. COThanks for the effort! Since I'm an Android newbie, I want to make sure I understood you correctly - is it okay to add / remove views and layouts from the main view of my activity pretty much anywhere in my code, and not just in the onCreate (I don't think I've seen examples for this), and then create and add fragments to them on the fly? It's a bit more than just "removing the fragments and adding them elsewhere", because I create a new layout for them.
      singulars
      1. PO
      1. USDannyA
    2. COThe goal is eventually to separate this Fragment logic to different "screen" classes, and have each class know about its own layout IDs, and put its own fragments in them. Then I can navigate from one "screen" to another via fragment transactions. e.g. hide all fragments of previous screen and show the new fragments instead. I must admit, this technique seems a bit strange, as it will flood my activity with empty layouts with invisible fragments... It seems like my goal is reasonable but I haven't found the correct design for it.
      singulars
      1. PO
      1. USDannyA
    3. COWell that's an interesting train of thought, but isn't this exactly what activities and their startActivity(Intent) method were made for? You get back button functionality for free, too.
      singulars
      1. PO
      1. USuser999717
 

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