Re: CoreData file format stability

On Jun 3, 2008, at 23:03 , Michael Ash wrote: On Wed, Jun 4, 2008 at 12:48 AM, Kyle Sluder <[EMAIL PROTECTED]> wrote: This is extremely unlikely to occur in practice. Apple is sensible enough to, in these sorts of circumstances, make these changes depending on which SDK you're compiling agai

Re: CoreData file format stability

On Tue, Jun 3, 2008 at 11:03 PM, Michael Ash <[EMAIL PROTECTED]> wrote: > Note that silently upgrading files when opening is the last thing > you'd want in this case. A file saved using FooApp 1.2 on 10.6 should > still work in FooApp 1.2 on 10.5. If you destroy my files so that they > no longer wo

Re: CoreData file format stability

On Wed, Jun 4, 2008 at 12:48 AM, Kyle Sluder <[EMAIL PROTECTED]> wrote: > On Tue, Jun 3, 2008 at 12:01 PM, Charles Srstka > <[EMAIL PROTECTED]> wrote: >> It also >> means that even for a Mac-only app you could end up with this really weird >> situation where an app running on a later version of OS

Re: CoreData file format stability

On Jun 3, 2008, at 7:18 PM, Ilan Volow wrote: But for the long term, the mac development community outside of Apple really needs to come up with their own ORM/persistance framework that can target a number of difference storage technologies (PostgreSQL, MySQL, SQLite), and provides adequat

Re: CoreData file format stability

I'd suggest you check out QuickLite http://www.webbotech.com/ for the time being. But for the long term, the mac development community outside of Apple really needs to come up with their own ORM/persistance framework that can target a number of difference storage technologies (PostgreSQL,

Re: CoreData file format stability

Thank you for your feedback. On Jun 3, 2008, at 5:34 PM, Ben Trumbull wrote: 1) The file format for saved files. I'd rather not make some proprietary/closed Microsoft-ish thing - I'd like it to be possible for other programs to read/write my file format, including hypothetical programs that mig

re: CoreData file format stability

1) The file format for saved files. I'd rather not make some proprietary/closed Microsoft-ish thing - I'd like it to be possible for other programs to read/write my file format, including hypothetical programs that might get written for other platforms so that my file format could possibly be read

Re: CoreData file format stability

On Tue, Jun 3, 2008 at 12:01 PM, Charles Srstka <[EMAIL PROTECTED]> wrote: > That's what I was afraid of. So it seems that by using CoreData, one loses > all control over his or her app's file format, which is a shame. There are plenty of circumstances in which you don't have control over the docu

Re: CoreData file format stability

On Jun 3, 2008, at 9:01 AM, Charles Srstka wrote: So it seems that by using CoreData, one loses all control over his or her app's file format, which is a shame. Although this w

Re: CoreData file format stability

On Jun 3, 2008, at 7:03 AM, Kyle Sluder wrote: On Tue, Jun 3, 2008 at 2:12 AM, Charles Srstka <[EMAIL PROTECTED] > wrote: 1) The file format for saved files. I'd rather not make some proprietary/closed Microsoft-ish thing - I'd like it to be possible for other programs to read/write my file f

Re: CoreData file format stability

On Tue, Jun 3, 2008 at 2:12 AM, Charles Srstka <[EMAIL PROTECTED]> wrote: > 1) The file format for saved files. I'd rather not make some > proprietary/closed Microsoft-ish thing - I'd like it to be possible for > other programs to read/write my file format, including hypothetical programs > that mi

CoreData file format stability

Okay, after many years of pretty much only doing software that had to run on very old versions of Mac OS X, I've finally decided to do some stuff that might require Tiger or maybe even Leopard, so I've been able to start exploring some of the various new features Cocoa has picked up over th