core data design pattern with different model transformations?
core data design pattern with different model transformations?
- Subject: core data design pattern with different model transformations?
- From: joe OneNinetyTwo <email@hidden>
- Date: Tue, 8 Aug 2006 02:44:46 -0700 (PDT)
I'm making the transition from Carbon (procedural) to
Cocoa (OO). So, I'm learning Objective C and Cocoa.
I'd like to use Core Data, but I'm confused a bit
about the design approach. My model has a large
data array (scientific data) that is processed in my
code. There are many different ways to process the
data, so I have designed different model objects to
manipulate the model data array in different ways.
It wouldn't be that different from an image processing
software with a variety of image filter methods.
What is the best way to implement this in Core Data?
In Xcode, it's clear how to add attributes and
relationships for the data model, but how would one
incorporation a variety of data transformation methods
(objects that act on the data model)?
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.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