I recently asked myself whether or not to use CoreData in Audipad. The program has to keep track of when a character is typed with respect to the currently playing/recording audio file. This sounds like it might be a good job for CoreData. However, I decided a few days ago it might be a little like swatting a hammer with a fly (strike that. reverse it.). CoreData also doesn’t care about order, so I would have to put indexes on everything and manually manage those. This didn’t sound like fun. Instead, I went with an NSArray and I am not regretting it. This article at MacDevCenter has put my mind at ease.
You can see my implimentation here. Basically it takes about 12 lines to record the data and about 11 to “play” it back. You can see a movie of it working here. Because of Ridiculous Fish’s great article on reverse engineering Apple’s NSArray implementation, I also think that this will scale quite well. Audipad is coming along!
Comments are closed.