Re: unconnected TextFields
Re: unconnected TextFields
- Subject: Re: unconnected TextFields
- From: publiclook <email@hidden>
- Date: Fri, 24 Oct 2003 11:33:47 -0400
On Friday, October 24, 2003, at 09:30 AM, Robert Clair wrote:
A few quick points since you seem to feel that I have asked a question
to which the answer is obvious:
<Quote>
...
<End Quote>
Perhaps I spent too much time in academia, but it is generally
considered good form and Helpful To The Reader to include an
attribution with a quote. As in what section of the docs did this come
from.
You are completely correct. It would have been better if I had
attributed the quotes to Apple's on-line documentation instead of
assuming that the source of the information would have been obvious to
you. In the future, I will endeavor not to quote the passage in the
documentation that answers your question without also citing the source
of the quote.
This is also well explained in this forum,
Maybe, but as the person making the error is probably unenlightened on
the topic and the symptoms do not have an obvious relationship to the
cause, searching for the answer can be a bit difficult. (Not to
mention the meta-problem that I don't know of a quoting or escape
mechanism that will convince the search engine on Mamasam that the
"not" in "not connected" is a word I want to search on and not a
Boolean operator.)
I am certainly not going to defend Apple's documentation. I have no
objection to them using large orange text in the margin of every page
telling you about the methods that will be called automatically if they
are present. They should also mention on every page that readers must
consult the superclass' documentation in order to fully understand the
interface of any class. In my experience, a large percentage of the
questions in this forum are not immediately found in the documentation
only because the questioner forgot to check the superclass
documentation. Many other object oriented systems have documentation
that lists every method a class provides regardless of whether the
method is inherited or not. Readers accustomed to those other
documentation systems may not be conditioned to check the superclass as
is required to effectively use Apple's documentation. To be fair to
Apple, a link to the superclass is prominent at the top of every class
description.
It is worth noting, however, that your specific question has been
answered in this forum. A quick search using mamsam would have given
you your answer.
Search for outlet AND nil AND IB at
http://cocoa.mamasam.com/search/results.php. The first hit is your
answer.
in comp.sys.next.*,
I mean no disrespect to anyone, but Next is a defunct company. With
the move to Apple Cocoa gains fame, wider exposure and many more
converts. A lot of the converts will be coming from a general Unix
background but no previous NextStep exposure. If successful
development requires haunting Next lists as well as Apple lists then
Apple should publicize this.
Clearly, successful development does not require haunting Next lists.
I was just trying to identify another resource you could use. I can't
win: I am criticized in this forum for not identifying sources and I
am criticized for identifying sources ;)
and many other places.
such as ?
My first stop is always google. I seldom start at Apple's developer
search interface. Google finds great information on Apple's pages, in
the archives of this forum, at the O'Rielly site, on Stepwise, and many
many other places. Google is Great!
probably ALL of the available Cocoa book mention this.
You are misinformed here. I have the two O'Reilly books: _Building
Cocoa Applications_ (BCA) and _Learning Cocoa with Objective-C
(LCO)_. I also have
Anguish, et al, _Cocoa Programming_ (CP). This is not all of them but
it is certainly typical of what an experienced developer coming from
another environment might buy. (Admission. I exaggerated. I weighed
them this morning on the food scale that I bought to try and keep
myself from eating too much pasta. They only come to 7 3/4 lbs, not 20
lbs.) A quick look in the indices reveals:
I don't understand. Are you angry with me for trying (but failing) to
help you, or are you angry with Apple for not highlighting a critical
design feature of their frameworks ? I am sorry if I was incorrect
about the ubiquity of the explanation of the design feature in
question. Many of us who have been writing NeXTstep/Openstep/Cocoa
code for years long ago internalized this aspect of the framework's
design. It is not always obvious to us exactly which critical design
aspects need to be highlighted and which may be discovered as needed.
Similarly, in the general sense, things that may seem baffling to one
person may seem obvious to another and visa versa. IMHO, Apple's
documents are good but could be improved. On the other hand, many
other questions (not yours) that come to this forum are easily answered
within the Getting Started link on Apple's site.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.