Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I found the information here (and elsewhere on StackOverFlow on this topic), and it got me to thinking about my previous answer. This just gets tedious if you have lots of top level objects.</p> <p>Then, it occurred to me that you could create a "helper" object, so I created a project to demonstrate the technique. Basically, the helper has an outlet for each object of interest in the view. The ViewController itself has two Helper objects (one for p, one for l) and you instantiate those in the NIB. On orientation changes, you switch the view controller's helper pointer to the appropriate helper, then update self.view. Its really simple (this text is harder).</p> <p>So, how would you start? Well it helps if you know a priori that you will need two separate view. Once you know that, take the Helper template in the referenced project below, adapt it, add it to your NIB, and then connect the help to the appropriate objects in the portrait view. The View Controller itself just has a reference to the two helpers, and a "curHelper" pointer. The Helper ivars are public, so the View Controller can reference items like "curHelper->label1.text = ... - the cost is a single pointer dereference (could just use properties too - your call).</p> <p>Also, you can directly connect IBActions from the objects in either view. So, lets walk through this:</p> <ul> <li>create the NIB</li> <li>create a Helper object, and instantiate one in the nib called Portrait</li> <li>add all the IBOutlets to the Helper object, handle then in dealloc, viewWillUnload</li> <li>put IBActions as normal in the View Controller</li> <li>wire up the NIB - Helper->Portrait view outlets, actions to the View Controller</li> <li>get it all working in Portrait</li> <li>add a new Helper object, call it Landscape</li> <li>dup the current portrait view, rotate it, and save it</li> <li>wire up the landscape Helper's outlets to the new landscape view (actions already set for you!)</li> </ul> <p>Obviously you need to from now on make duplicate changes, but in any dual nib scheme you would have to do that. In the above technique, all outlet names stay the same.</p> <p>The View Controller needs to send "viewDidUnload" to both helpers when it receives it, and to dealloc the Helpers (which then dealloc their outlets).</p> <p>NOTE: I just put this together to see how it looked. If you want to see the code and a really small demo, you can download it from public dot me dot com slash dhoerl, in the iPhone folder with name Helpers.zip. I'll update this and this text if needed.</p>
    singulars
    1. This table or related slice is empty.
    1. POiPad/iPhone multiple orientations best practice?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid H
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POiPad/iPhone multiple orientations best practice?
      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. VTAcceptedByOriginator
    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. VTUpMod
    1. COThis is a pretty good way to deal with the 2 references problem. I still don't feel good about the dual nib approach since you have to have two of every subview in memory (or recreate them on orientation changes), and you couldn't animate the subviews. So far, I am just designing my layout so that autoresizing can handle rotation - a little more limiting, but less work/clutter.
      singulars
      1. PO
      1. USinitlaunch
    2. COThanks a lot, this is a pretty good idea.
      singulars
      1. PO
      1. USpt2ph8
    3. CONice approach. (I don't need 15 or more characters to say "Nice approach.")
      singulars
      1. PO
      1. USMustafa
 

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