Databases
StackOverflow2013
Postsdbo
PODocument Based App with Core Data vs plain Core Data app?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PODocument Based App with Core Data vs plain Core Data app?
    primarykey
    data
    text
    <p>I am trying to understand the key differences between these two types of Core Data application templates.</p> <p>My understanding is that with a document based core data app you get access to NSDocument instances and a lot of document based behaviors for free (save dialogs, undo, etc).</p> <p>Assuming I want to create an application that is more "Project" based and not necessarily focused on creating individual savable documents should I still use Core Data with Documents?</p> <p>To be more concrete, I am trying to build a simple CMS application using core data and that outputs html pages in a structured way. The idea of the app would be focused on "sites" that are really projects and not single documents. The projects contain a consolidated model for various posts, pages, sidebar content, and whatever content might need to go into a website. But the app doesn't save individual pages as documents in the traditional sense. I want a unified model of the all the project data and provide export functionality where the entire application model would become expressed as a set of html documents in a specified project folder.</p> <p>This is both a learning exercise and something I want to try and build for myself.</p> <p>Any tips on specific documentation to read? In particular information about "Project" based cocoa apps, and useful samples and tutorials.</p> <p>It is conceivable that the CMS data model could be stored in a single Core Data document but that doesn't necessarily seem right from an architectural point of view.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USGordon Potter
    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. PODocument Based App with Core Data vs plain Core Data app?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PODocument Based App with Core Data vs plain Core Data app?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PODocument Based App with Core Data vs plain Core Data app?
      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