> On 2015 Feb 03, at 08:02, Steve Mills wrote:
>
> On Feb 3, 2015, at 06:51:35, Dave Fernandes
> wrote:
>>
>> Mike Abdullah’s BSManagedDocument.
>
> Too bad it always saves as a package
Actually, that’s an advantage, because flat files do not play well with the new
Write Ahead Lookup (WAL)
On Feb 3, 2015, at 06:51:35, Dave Fernandes wrote:
>
> NSPersistentDocument is not designed to work with “modern” features like
> private queue MOCs. So I expect you are going to be playing whack-a-mole if
> you go this route. I just switched to Mike Abdullah’s BSManagedDocument. It
> is like
NSPersistentDocument is not designed to work with “modern” features like
private queue MOCs. So I expect you are going to be playing whack-a-mole if you
go this route. I just switched to Mike Abdullah’s BSManagedDocument. It is like
UIManagedDocument, but for OS X. If you don’t have any customer
On Feb 2, 2015, at 17:36:22, Roland King wrote:
>
> get the NSManagedObjectContext the document creates for you with [ super
> managedObjectContext ], get the store coordinator with [ managedObjectContext
> persistentStoreCoordinator ], create your own MOCs on that store, hold on to
> the MOC
> On 3 Feb 2015, at 04:25, Steve Mills wrote:
>
> On Jan 31, 2015, at 12:00:03, Jerry Krinock wrote:
>>
>>
>>
>> I liked this one [1] by Aaron Douglas (all in Swift) when I was needed to do
>> a presentation on Core Data last September. And then, in a rage of NIH [2],
>> I wrote my own [3
On Jan 31, 2015, at 12:00:03, Jerry Krinock wrote:
>
>
>
> I liked this one [1] by Aaron Douglas (all in Swift) when I was needed to do
> a presentation on Core Data last September. And then, in a rage of NIH [2],
> I wrote my own [3] instead, in Objective-C. The one Swift alternative file
> On 2015 Jan 30, at 22:01, Steve Mills wrote:
>
> Isn't there just an example of a document-based app that implement concurrent
> Core Data importing and all that jazz?
I liked this one [1] by Aaron Douglas (all in Swift) when I was needed to do a
presentation on Core Data last September. A
Isn't there just an example of a document-based app that implement concurrent
Core Data importing and all that jazz? I see tons and tons of little scraps of
info and examples (which end up not working with my app as it is because it was
written based on Apple's outdated documentation), but not t
> On 31 Jan 2015, at 01:20, Steve Mills wrote:
>
> I'm trying to learn Core Data. I have a working document model hooked up to a
> table view (OS X). I have an import method that uses FSDirectoryEnumerator to
> add an object for each file in the folder. Oky doke! But that blocks for a
> few s
I prefer the GCD method but there are a few details that cause people trouble
when combining GCD with CoreData.
1. A named GCD queue may guarantee serial processing but it does not guarantee
that it will always use the same thread
2. NSManagedObjectContexts are not thread safe, and it’s not just
I'm trying to learn Core Data. I have a working document model hooked up to a
table view (OS X). I have an import method that uses FSDirectoryEnumerator to
add an object for each file in the folder. Oky doke! But that blocks for a few
seconds while it loops. So I'm trying to make it threaded. On
11 matches
Mail list logo
