• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: CoreData document based app with single source
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CoreData document based app with single source


  • Subject: Re: CoreData document based app with single source
  • From: Niko Matsakis <email@hidden>
  • Date: Sat, 10 Dec 2005 15:26:35 +0100

This sounds to me like you want basically want a "document" to be a set of invoices, probably with associated account information. You would like need several window controllers which will be associated with your document, one for each kind of window.

This is no doubt covered in the documentation under writing document based applications, which hopefully explains it in more detail than I have. :)


Niko

On Dec 10, 2005, at 10:51 AM, Mayo Jordanov wrote:

Hello,

I'm trying to figure a few things out about Document Based apps. I understand normally there would be a file per document. For the sake of example, if I make a simple invoice application, there will be a CoreData datafile (XML/Binary/SQLite) with some invoice information such as date, customer address, and items.

Now, how would this work if I wanted to have a single CoreData datafile with multiple invoices in it? This solution makes more sense to me as it's much easier to search, enforce unique invoice numbers, etc. From what I can tell the CoreData Document Based app project template expects to have file per document.

I can think of few ways around this, such as putting a small table of existing invoices on top of each document, and thus being able to select from multiple invoices (if I want to look in past) or create a new invoice. Another one would be to make a separate window that could be opened from the application menu where invoices could be looked up and then programatically generate MyDocument windows/objects with each invoice, however wouldn't this be breaking the Document based design? Should I not be using document based design for this at all?

I'm not looking for code or anything here, just trying to solve this at conceptual level...

Thanks in advance,
mayo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden
References: 
 >CoreData document based app with single source (From: Mayo Jordanov <email@hidden>)

  • Prev by Date: Audio & Video Capture
  • Next by Date: Re: Slightly OT: simulating a dock icon click via an AppleEvent (or otherwise)
  • Previous by thread: CoreData document based app with single source
  • Next by thread: Re: CoreData document based app with single source
  • Index(es):
    • Date
    • Thread