Re: Design Question: Pro & Cons of KVC/KVO
Re: Design Question: Pro & Cons of KVC/KVO
- Subject: Re: Design Question: Pro & Cons of KVC/KVO
- From: Negm-Awad Amin <email@hidden>
- Date: Thu, 21 Aug 2008 16:50:10 +0200
Am Do,21.08.2008 um 16:41 schrieb Oleg Krupnov:
Thanks Amin for responding.
You are correct that there's no need to reinvent the wheel, and that's
exactly what I'd like to avoid, that's why I am now re-reading about
KVC/KVO and reconsidering it.
So, does everybody really always use KVC/KVO for implementing MVC, in
all projects?
There are some situation, where glue code is neccessary. Imagine a
outline view that has a items lib and some groups, where you can place
items from the lib and see them in the outline view by opening the
isclosure. Or you have items from different entities there.
But even in this case it helps to use KVO on the parts to get
synchronized.
Is this the recommended best practice?
BTW does anyone use Core Data?
You're joking?
I've watched the video tutorial and it
looks like too much magic. I would never guess how to make Core Data
work for a drawing application like the Sketch. Is Core Data rather
for database+forms apps?
1. Core data is not a database.
2. I think, that you are new to cocoa and a little bit afraid of the
"magic" things. Hey, dive into it, read documentation, try a little
bit coding and so on. There is no magic. It's just new land for you.
Thanks.
Cheers,
Amin Negm-Awad
email@hidden
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden