Note that there are some explanatory texts on larger screens.

plurals
  1. POReproducing Honeycomb GMail UI with fragments
    primarykey
    data
    text
    <p>I'm trying to reproduce Honeycomb GMail UI with fragments and can't. Here's what I want</p> <p>Initial state:</p> <pre><code>+--------+---------------+ | | | |Accounts| Folders | | | | +--------+---------------+ </code></pre> <p>after folder is selected:</p> <pre><code>+--------+---------------+ | | | |Folders | Items | | | | +--------+---------------+ </code></pre> <p>where Accounts, Folders and Items are fragments. (Obviously back button should go to initial state)</p> <p>I tried the following layout:</p> <pre><code>&lt;LinearLayout xmlns:android="http://schemas.android.com/apk/res/android" android:layout_width="match_parent" android:layout_height="match_parent" android:orientation="horizontal" android:id="@+id/root"&gt; &lt;FrameLayout android:id="@+id/left_pane" android:layout_weight="1" android:layout_width="0px" android:layout_height="match_parent" /&gt; &lt;FrameLayout android:id="@+id/right_pane" android:layout_weight="1.6" android:layout_width="0px" android:layout_height="match_parent" /&gt; &lt;/LinearLayout&gt; </code></pre> <p>Unfortunately this doesn't work because I can't move my Folders fragment from right pane to the left pane (fragment can be added only once). I can create new Folders instead, but that is quite resource wasteful, needs careful state management (especially when back button will be pressed) and doesn't look the way I want it to look.</p> <p>I tried using 3 FrameLayouts (left, middle, right with weights 1, 1.6, 2.56) but I can't make the FrameLayout to collapse when fragment is not shown. Any help is really appreciated </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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.
 

Querying!

 
Guidance

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