Re: AppKit source available as reference?
Re: AppKit source available as reference?
- Subject: Re: AppKit source available as reference?
- From: Karl Goiser <email@hidden>
- Date: Sun, 1 Jul 2001 11:54:28 +1000
Hello,
I certainly appreciate the efforts of Scott and Bill et al in making
tutorials to help us newbies get into Cocoa programming - thank you!
I think tutorials are great for getting people up to speed.
My problem is going beyond that. Given a particular problem, how do
I find the solution?
For example, here's a question I asked in the list a few weeks back:
"How do I create an FSSpec from an NSString containing a full path
name"? Several people responded and I was able to obtain a solution
- thanks.
But the real problem with this is that I couldn't see how to find the
solution myself. And, judging by the number of similar questions on
this list, I am not alone.
The reason I'm making so much about having the source code and a good
browser is that when I had them, I was able to solve my own problems
by looking through others' code - including system code. Now, I'm
not saying that there aren't alternatives to this, I just don't have
experience of any. And the problem with tutorials in this area is
that you have to have lots and lots of tutorials to cover all aspects
of Cocoa, they are necessarily long and take time to work through and
you still have the problem of persistence of memory ("I remember
seeing some code on this topic. Which tutorial was it in?").
It seems like the only solution to this at present is to have all of
Cocoa committed to memory.
So, I'm not saying that the tutorials are bad - they're great - and
I'm not saying that there is anything wrong with Cocoa - it looks
quite complete and elegant*. I just think that there is an aspect to
the developing of Cocoa code that is missing.
Karl
*P.S. Who decided to use setObject:forKey: instead of at:put:?
--
----
Klaatu barada nikto