Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I recently had the same issue in one of my apps (navigation style) and the way I solved it is fairly simple.</p> <p>I had a user_type flag in my JSON response, and depending on that flag I would push a different view controller.</p> <p>For example, given my JSON response is stored in a NSMutableDictionary called "response"</p> <pre><code>if ([response objectForKey:@"account_type"] == 1) { /* initialize user_type 1 viewController */ [self.navigationController pushViewController:userType1ViewController animated:YES]; else if ([response objectForKey:@"account_type"] == 2) { /* initialize user_type 2 viewController */ [self.navigationController pushViewController:userType2ViewController animated:YES]; } </code></pre> <p>You can have as many different user_types as you want.</p> <p><em>Editing after clarification in comments</em></p> <p>You will likely be manually drawing these views.</p> <p>I would subclass UIView for each of the different question types you have listed (including properties for common elements like question title, choices, etc). Assuming that questions with the same question type will have the same layout.</p> <p>Then you can cycle through your JSON response (once it's in an array or dictionary) and lay it out.</p> <p>If it's a multiple choice question, make a new multipleChoiceQuestion view, add its properties, then addSubview to the main feed view. Then, for your next view, you will need to set the frame to be:</p> <pre><code>nextQuestion.frame = CGRectMake(0, 0 + firstQuestion.frame.size.height, height, width); </code></pre> <p>This will ensure that your second question is drawn right below the first question.</p>
    singulars
    1. This table or related slice is empty.
    1. POBuilding a data driven UI
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USPeter Andersen
    1. USPeter Andersen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POBuilding a data driven UI
      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
    1. COThanks for the response. But my needs are a bit more complicated. I at any point of time would have no idea what to expect from the response as far as the quantity of data is concerned. I have Q&A's coming in the response for which I've decided on textViews. Rating scales coming in for which I've setup UISliders. Multiple option Q&A's coming in and I've got UITableViews/UIPickerViews. But I will know how many of each only when I parse the response. How do I layout my view accordingly?
      singulars
      1. PO
      1. USBourne
    2. COAm I clear? In case if I'm not its like this. I may receive any number of Q&A items in the response AND of any type (multi-choice,rating scale,simple Q&A). I won't know that until the parsing is done. Only then will I know how many textviews, sliders and tables or pickers to setup. Its not the question of loading fixed different view controllers based on simple decisions. Its more about laying out the different subviews on the viewcontroller based on the response. I may need to setup 1 one of each type, or just 1 textview or I may need 10 textviews, 5 sliders and 3 tables. Got it?
      singulars
      1. PO
      1. USBourne
    3. COedited my response. Let me know if this helps. Are you comfortable with subclassing UIView and drawing things manually in drawRect?
      singulars
      1. PO
      1. USPeter Andersen
 

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