Should I use Core Data?
Should I use Core Data?
- Subject: Should I use Core Data?
- From: David Catmull <email@hidden>
- Date: Thu, 20 Apr 2006 07:47:06 -0700
I've been working on a drawing app (the SVG-based one I mentioned a
few weeks ago), and recently I've been considering a move to Core
Data. So far I'm doing everything with NSArrays and NSDictionaries. I
didn't consider Core Data at first just because I didn't realize that
it can be used in this kind of application. But I'm not yet convinced
that it's worth the trouble.
There are two main points that leave me doubtful. First, my file
format is SVG, so from what I've gathered none of CD's file storage
stuff applies. Second, as this is a drawing application, I have a lot
of "non-standard attributes" - rects, colors, paths, etc. The
documentation makes that sound inconvenient.
It would be nice to have the built-in undo support, but it's actually
not clear to me what other benefits I would get. The documentation
occasionally mentions the hypothetical example of a Core Data drawing
app, but it sure would be nice to have some sample code, like a CD
version of Sketch.
What are the deciding factors in the decision to switch to Core Data?
This app is pretty young, so the switch probably wouldn't be to costly.
And as this is an open source undertaking, I'll take this opportunity
to do another call for participants. The goal is to make something
like Illustrator, but with SVG instead of PostScript, or like
Inkscape but with a focus on illustration rather than SVG authoring.
At the moment, shapes, paths, and gradents are working (as far as
rendering goes), and I'm just beginning to work on object
manipulation and drawing tools.
http://sf.net/projects/xvg
--
David Catmull
email@hidden
http://www.uncommonplace.com/
_______________________________________________
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