Databases
StackOverflow2013
Postsdbo
POQuestions about iPhone app structure - Core Data, Views, Modal Views etc
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POQuestions about iPhone app structure - Core Data, Views, Modal Views etc
    primarykey
    data
    text
    <p>About a month ago my wife and I came up with a good idea for an iPhone app, so I set about thinking of how the app would work from a users perspective and about a week ago I opened up XCode for the first time and began to develop. </p> <p>Before I get too stuck into the writing of the app, I want to make sure I have some key concepts clear in my mind, specifically related to architecture.</p> <p>FYI, as a principle I would like to try to create as much of my app programmatically (specifically the UI) so that I have a thorough understanding of what's going on. Later on I might use IB as a tool to speed up UI development (applies at the moment because I'm using TableViews as opposed to static views). </p> <p>View Controllers</p> <ul> <li><p>So UINavigationControllers are generally not sub-classed and are created as a property in the AppDelegate and are the main 'sub-view' of the MainWindow.xib. </p></li> <li><p>The UINavigationController controls a stack of views, and is usually initiated with a root view controller.</p></li> <li><p>The navigation controller is generally referenced and messaged from within the current/top view controller as [self navigationcontroller] which is a read-only property of the UIViewController parent class. </p></li> </ul> <p>Core Data</p> <ul> <li><p>The Managed object context is the main control point for accessing data in the model but it is generally not used directly and instead fetch requests are used to return arrays, sets or dictionaries of data objects which are then used by the view controllers to present and manipulate data.</p></li> <li><p>the context is created as a property in the app delegate and is then passed to the root view controller upon start up which itself passes it to subsequent views in the stack before telling the navigation controller to change the view (for example when a cell is tapped). </p></li> </ul> <p>So it's taken me a week to get to here, I can create my model, fill it with data and display it on a table view but I have not been able to find much on Modal Views when you want to edit data, specifically how to design modal views (if there's any specific difference to normal views)?</p> <p>Also, I'm not entirely sure of the whole 'binding' of data to view objects what it does and how to do it programmatically?</p> <p>Many thanks for your comments, suggestions in advance. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGlynton
    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.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POQuestions about iPhone app structure - Core Data, Views, Modal Views etc
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POQuestions about iPhone app structure - Core Data, Views, Modal Views etc
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POQuestions about iPhone app structure - Core Data, Views, Modal Views etc
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

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