Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <blockquote> <p>now I perform an action in the detail that needs to finish it</p> </blockquote> <p>That is unusual flow for the master/detail pattern. Normally, the detail persists until the user taps on something else in the master list. I could see your proposed flow for a delete operation on the item being viewed, though.</p> <blockquote> <p>I was thinking about a callback that both activities would implement and the single pane would just finish it self and therefore finishing the fragment, and the dual pane would just pop the fragment.</p> </blockquote> <p>That is a fine answer.</p> <blockquote> <p>Isnt this much overhead?</p> </blockquote> <p>No. Define an interface that all activities hosting your fragment must implement. You might consider using the contract pattern to help enforce that:</p> <pre><code>import android.app.Activity; import com.actionbarsherlock.app.SherlockFragment; // from https://gist.github.com/2621173 public abstract class ContractFragment&lt;T&gt; extends SherlockFragment { private T mContract; @SuppressWarnings("unchecked") @Override public void onAttach(Activity activity) { try { mContract=(T)activity; } catch (ClassCastException e) { throw new IllegalStateException(activity.getClass() .getSimpleName() + " does not implement " + getClass().getSimpleName() + "'s contract interface.", e); } super.onAttach(activity); } @Override public void onDetach() { super.onDetach(); mContract=null; } public final T getContract() { return mContract; } } </code></pre> <p>(code based on <a href="https://gist.github.com/2621173" rel="nofollow">a gist from Jake Wharton</a> of ActionBarSherlock fame)</p> <p>Here, <code>T</code> is the name of the interface. Your fragment would inherit from this and call <code>getContract()</code> to retrieve the interface implementation object, on which you call your callback method. Runtime overhead will be on the order of a few dozen instructions at most -- nothing you will need to worry about.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow to finish fragment in Master/Detail flow?
      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. POHow to finish fragment in Master/Detail flow?
      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. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    1. COI was thinking about having a master/detail, with Add/Edit action on the list, that would put a form fragment to where the detail fragment was, so when you submit the form, it would kill it self and went back to the normal detail fragment (tablet). Deleting from the detail fragment is also the case. I just didnt know wether do it with callbacks so wrapper activities control the fragment, or just an if statement inside fragment to figure out who is hosting me, as M-WaJeEh proposed.
      singulars
      1. PO
      1. USurSus
    2. CO@VlastoBennyLava: Ah, OK, your plan makes sense. Personally, I prefer to keep my fragments ignorant of the hosting activity, and the `instanceof` approach requires fragments to know about specific activity classes. Hence, I prefer the interface approach outlined in my answer. Both will work, though.
      singulars
      1. PO
      1. USCommonsWare
    3. COOn a another topic, could you please take a look at my other question? http://stackoverflow.com/questions/14990269/where-to-handle-cab-actions-of-a-list-item-that-are-common-with-detail. Thanks.
      singulars
      1. PO
      1. USurSus
 

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