Re: All these newbie questions that are answered by documentation
Re: All these newbie questions that are answered by documentation
- Subject: Re: All these newbie questions that are answered by documentation
- From: "Mark's Studio" <email@hidden>
- Date: Fri, 9 Nov 2001 22:04:42 +0100
Yes im a newbie
But i spend hours serching the documentation both new Cocoa and old
NextStep
and anything ObjC to try and find anything that can show me how to do a
specific thing
im trying to implement, before i ask this list.
I think i've come pretty far look at "Mark's AddressBook",
the most difficult part in making that was finding the information
for implementing the different features i wanted,
and i would like to thank the people on this list who helped
when it was needed. yes i also asked for things that was in the
documentation, but i was looking in the wrong place.
what i've learned most from is all the examples i could
find.
So i often think would it be possible to hire any of you experienced
Cocoa masters
to code what im looking for.
Thanks
On fredag, november 9, 2001, at 09:31 , Erik M. Buck wrote:
>
It seems to me that most of the newbie questions that are easily
>
answered by
>
documentation and keep recurring in this forum and others are due to 4
>
general causes:
>
>
1) People seemingly refuse to look at the super class's documentation
>
>
2) Sherlock sucks so bad that people will not use it to search the
>
documentation and newbies can not be bothered to use MTLibrarian or
>
another
>
search tool.
>
>
3) There is a lack of good concepts and overview documentation. Newbies
>
refuse to just dive in and read the details about classes. They seem to
>
want broad overviews that at least tell them where to look. Combined
>
with
>
the fact that newbies don't even know the terminology to use when
>
searching,
>
they can not find anything.
>
>
4) Familiarity with C++ and MFC has warped their minds to the point that
>
they just can not understand a dynamic language like Objective-C and
>
flexible frameworks like the Application Kit. A refusal to change
>
mindsets
>
locks people out of Cocoa.
>
>
>
I see several solutions:
>
For 1), Apple could include every method from every superclass in the
>
documentation for every class. That would only expand the size of the
>
documentation by a factor of 5 or so, but then people would not have to
>
look
>
in more than one place as often.
>
>
For 2), Apple could/should just scrap the shitty Sherlock and revive
>
Digital
>
Librarian or something better. People could also start using google.
>
Google is very handy for searching Apple's on-line documentation.
>
>
For 3), more is better, but most of the newbies posting have never
>
bothered
>
to read Object Oriented Programming and Objective-C. I don't know how
>
we
>
can expect these people to read any kind of overview if they are not
>
willing
>
to even learn the language of the frameworks.
>
>
For 4) If people will not change and/or can not see the advantages of a
>
different way of doing things then I don't think Cocoa will ever appeal
>
to
>
them. I suggest that we forward all such people to the Carbon lists.
>
_______________________________________________
>
cocoa-dev mailing list
>
email@hidden
>
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
>
>
Peter Mark
Mark's Recording Studio A/S
Faelledvej 19 b DK2200 N
Copenhagen Denmark
Tel: +45 35366078 Fax: +45 35366038
www.marks-studio.dk
email@hidden