Ken,
Okay, that makes perfect sense. You are right, I was storing the pipe-
separated string of values to avoid needing another DB table for
single values that would not surpass more than 2 or 3 per record.
However, your and Kyle's response now make it obvious that the pipe-
string is not t
On Jun 14, 2009, at 2:34 PM, Chris Tracewell wrote:
On Jun 14, 2009, at 11:27 AM, Kyle Sluder wrote:
NSDocument is what's known as a "model-controller" object. Your
actual model is the pipe-separated values; NSDocument allows you to
perform operations on that model. As such, I'd probably exp
Thanks Kyle, I should've noted this is a non-document based app. That
said, I think your suggestion would imply to let the controller to
expose its own array property of the model's pipe-separated property?
Chris
On Jun 14, 2009, at 11:27 AM, Kyle Sluder wrote:
NSDocument is what's known
NSDocument is what's known as a "model-controller" object. Your
actual model is the pipe-separated values; NSDocument allows you to
perform operations on that model. As such, I'd probably expose an
NSArray property for my list of things, and only do the
pipe-separation when reading from or writin
I have many occasions when a model's property needs to be transformed
to another type for use in a view. In this case I have a string of
pipe separated values that need to be transformed into a
NSMutableArray, manipulated in the interface and then converted back
to the pipe separated string
