On Jun 17, 2005, at 1:00 PM, Keith Blount wrote:
I know that Core Data could probably do a lot of this fairly easily, but there are issues such as having to use undocumented API methods such as -observedObject in order to support variable row heights
That's the only one you need to use, and it's pretty low risk.
and the fact that using Core Data with NSTreeController means that you cannot use NSOutlineView's datasource persistent state methods
Why would you need to if using Core Data?
there are a *lot* of workarounds required at the moment as I understand it.
Hmmm, I don't really think so. The -observedObject is the only one that occurs to me, and it's one line of code.
My question is: if you are starting a project and are happy only to target Tiger and above only, should you be using Core Data for most projects
I think so. It saves you a lot of manual labor. Core Data isn't right for every imagineable project, but it sounds like yours deal with management of a lot of individual objects. Core Data excels at this.