• 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: Persistent Stores and Packages ...
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Persistent Stores and Packages ...


  • Subject: Re: Persistent Stores and Packages ...
  • From: mmalcolm crawford <email@hidden>
  • Date: Mon, 23 May 2005 22:03:40 -0700


On May 23, 2005, at 6:18 PM, SA Dev wrote:

Thanks for the heads-up. So ... can I surmise the documentation was expected to be self-explanatory because if the instructions it gives worked, they'd be 100% correct? :-D

More-or-less -- at least they should indicate the proper starting-point.

Cool. CORE DATA is wrong, not ME. ;-) I actually completely ruled that possibility out of my head because of the constant stream of "I can't make this work so it must be a Cocoa bug" posts. I was too afraid of becoming a statistic.

That depends on how far you got. If you'd tried to migrate the store and found that it disappeared out from under you, then yes that would have been Core Data's fault. If you haven't got that far, then that was an incomplete assignment and you'd probably get a check- minus :-) (I should be grading at the moment...!)

Anyway, by document architecture, I assume you don't mean completely rewriting NSDocumentController, et al. There's got to be something someone can recommend that would make this not as monumental a task as it sounds ...

This time I'm erring on the side of caution. There's an inconsistency between the way that NSDocument works and the way NSPersistentDocument wants to work such that you should not expect to be able to create an application based on NSPersistentDocument that uses file wrappers. I need to do some more investigation to see if you might be able to extend NSDocument instead...

I would like to know, however, if my target's Document Types (I said file types earlier, sorry for the confusion) are set correctly as I described them above ... which by association makes me wonder if there's some creative jiggling we can do there to get around this problem.

Sorry, no.

mmalc

_______________________________________________
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: 
 >Persistent Stores and Packages ... (From: SA Dev <email@hidden>)
 >Re: Persistent Stores and Packages ... (From: mmalcolm crawford <email@hidden>)
 >Re: Persistent Stores and Packages ... (From: mmalcolm crawford <email@hidden>)
 >Re: Persistent Stores and Packages ... (From: SA Dev <email@hidden>)

  • Prev by Date: Re: SyncConduit.framework
  • Next by Date: glyphWithName: in Tiger
  • Previous by thread: Re: Persistent Stores and Packages ...
  • Next by thread: ANN Testers Wanted
  • Index(es):
    • Date
    • Thread