But the Core Data documentation starts like this:
...
Core Data is not an entry-level technology.
...
You should not simply try to read [The Core Data Programming Guide]
straight through to understand Core Data.
...
Do not attempt the NSPersistentDocument Core Data Tutorial unless or
until you al
Thanks, Brent, Jeffrey, I.S. and everyone else.
My apologies to the list for the inappropriateness of my light-hearted
initial post.
I'm sure that Core Data isn't really as bad (to learn) as it might
initially seem.
I am equally sure that 'The Documentation' could be improved - but
then
The best way to learn all this stuff is a step at a time.
On Sat, Oct 3, 2009 at 11:14 AM, Colin Howarth wrote:
> This is a long (but witty and interesting) rambling post about design,
> apple documentation, learning Obj-C & Cocoa and so on.
>
>
> I'm writing a raytracing / lens design program.
On Oct 4, 2009, at 10:39 AM, Jeffrey Oleander wrote:
>> It's not a toy language or API by any stretch of the
>> imagination.
>
> But Core Data seems to be.
Please expand on this, and why you feel it to be the case.
A great many people are using Core Data successfully in their applications on
b
> >> Anyway, I ended up with a graph of Objects and
> methods which looks nice and consistent and -- clean!
> :-)
>
> I'm happy with my model. And I'm certain it would benefit
> from Core Data.
>
> > A1: A lot of beginners complain about this. A lot of
> intermediate to pros recognize that the do
On 3 Oct, 2009, at 23:51, Klaus Backert wrote:
On 3 Oct 2009, at 22:06, Colin Howarth wrote:
If you use dot notation and properties, you are using the -value
and -setValue: accessor methods, which is KVC compliant and means
that KVO bits will get notified, no?
No.
From the documentation "
On 3 Oct, 2009, at 23:05, Greg Guerin wrote:
Colin Howarth wrote:
This is basically my first serious attempt at a real Cocoa program,
This statement has no context.
What less-than-serious attempts have you made at less-than-real
Cocoa programs? Were all those attempts successful, i.e. d
Colin Howarth wrote:
This is basically my first serious attempt at a real Cocoa program,
This statement has no context.
What less-than-serious attempts have you made at less-than-real Cocoa
programs? Were all those attempts successful, i.e. did they result
in a working program for whatev
On 3 Oct, 2009, at 18:12, Izidor Jerebic wrote:
Extremely simplified way of describing CoreData is "easy to use
database". So if you have something like a personal library
application with list of books, CDs, DVDs etc. that can go into
1000s of items and application has GUI for searching,
On 3 Oct, 2009, at 17:39, Volker in Lists wrote:
have you filled a bug report? - Yes, can do this for documentation.
Might lead to the responsible person fastest. So, if not yet done,
hurry and do so!
But the documentation isn't wrong. It isn't even unclear, if you know
exactly what its tr
On 3 Oct, 2009, at 21:31, Mike Abdullah wrote:
Well for a start your translation is wrong. Being able to do this:
baz = foo.bar;
foo.bar = baz;
is an Objective-C 2.0 feature – Dot Notation. It is completely
orthogonal to Key-Value Coding.
Dot Notation works by the compiler figuring out whi
On 3 Oct, 2009, at 18:08, I. Savant wrote:
[ big, massive, much-needed snip ]
hmmph.
FOCUS!!!
I get that you're trying to be witty, but I was forced to skim much
of your "question" because it's mostly rambling. Witty is fine. Even
a good dose of funny irrelevance, but you do need at l
On 3 Oct 2009, at 20:20, Colin Howarth wrote:
OK, skipping the melodrama, there's something wrong with the Apple
documentation,
but I can't quite put my finger on it.
The Perl man pages on nested data structures, say a dictionary
containing arrays containing
other dictionaries which are ac
On 3 Oct, 2009, at 18:07, Sherm Pendley wrote:
On Sat, Oct 3, 2009 at 11:14 AM, Colin Howarth
wrote:
WARNING! Do not even ATTEMPT the NSPersistentDocument Core Data
Tutorial!
Your very MIND is in MORTAL DANDER!
Overreact much? We're talking about technical documentation, not an
H.P. Lov
On 3.10.2009, at 17:14, Colin Howarth wrote:
Now that's a shame, because save: load: sounds like a persistent
document to me. But if even Apple's documentation says WARNING, Do
NOT attempt to read the Programming GUIDE in order to understand
Core Data -- well, I believe 'em!
On the o
On Oct 3, 2009, at 11:14 AM, Colin Howarth wrote:
This is a long (but witty and interesting) rambling post about
design, apple documentation, learning Obj-C & Cocoa and so on.
[ big, massive, much-needed snip ]
FOCUS!!!
I get that you're trying to be witty, but I was forced to skim m
On Sat, Oct 3, 2009 at 11:14 AM, Colin Howarth wrote:
>
> But the Core Data documentation starts like this:
>
> ...
> Core Data is not an entry-level technology.
> ...
> You should not simply try to read [The Core Data Programming Guide] straight
> through to understand Core Data.
> ...
> Do not a
This is a long (but witty and interesting) rambling post about design,
apple documentation, learning Obj-C & Cocoa and so on.
I'm writing a raytracing / lens design program. This is basically my
fist serious attempt at a real Cocoa program, and whist I'm quite
happy with C and Perl, I don'
18 matches
Mail list logo
