Re: [Q] Bindings, FilteringController and KVC compliance
Re: [Q] Bindings, FilteringController and KVC compliance
- Subject: Re: [Q] Bindings, FilteringController and KVC compliance
- From: "Peter.Teeson" <email@hidden>
- Date: Fri, 17 Sep 2004 09:57:53 -0400
On Sep 17, 2004, at 02:47, mmalcolm crawford wrote:
I am suspicious that there may be an undocumented thing going on
here but don't have a clue where to look for this.
There are undocumented things going on here all right, but not at
this comparatively easy level :)
Does MMALC care to comment (please)?
I guess he keeps his temper tightly under control, not daring to say
what he would like to :)))))
Umm, the only thing here that might cause any anger or frustration is
myself, for having left the "Inspector" in the example without drawing
attention to it.
Peter: I trust that Ondra's analysis reassures you that there is
nothing else undocumented happening?
Yes indeed. See my reply to him.
The general point here is one that applies to all Cocoa development,
but is more important with the advent of bindings.
Traditionally developers are used to dealing with code.
If something goes wrong with the application, the first instinct is
to look through your source files to try to determine the cause.
Amen. As a former mainframe systems programmer that's where I looked. I
have a good story to tell about that but it's not entirely relevant to
this list.
With Cocoa, however, an increasing proportion of the functionality of
an application is determined by non-code files.
If inspection of code fails to yield a solution to a problem, you
should get into the habit of looking at other auxiliary files,
primarily nibs.
Well yes this is indeed the case here. (This old dog still has to learn
soe new tricks).
mmalc this is not a criticism of your example - not at all - I am
grateful you have made them to help us slow learners.
My guess is that I am not the only one who struggles with getting a
mental picture of how bindings work.
I do believe that part of it is because there is much that is "hidden"
in the sense of not being readily visible.
In the "old days" we used to make flow charts and heavily comment our
code.
That way we could reasonably rapidly re-learn what we had coded 6
months earlier when later we had to enhance or correct it.
Or more to the point when we had moved on and someone else had to
maintain the code cold turkey.
(When I managed teams one of the tests was to extract the comments from
the source and see if we could re-create the code from them).
With .nib files (and for that matter with resource files under OS 9 and
prior) that habit changed. For me I just have to learn some new
approaches in OS X.
In a way this confirms one of my earlier comments about "hidden"code,
in the sense of not immediately apparent, when it comes to bindings.
In the absence of other tools to help us mortals (aside from the find,
grep etc which few of us think to use, or have forgotten to use with
the advent of GUI's)
it is clearly the author's responsibility to clearly document their
work for future generations. <smile>.
I repeat:
mmalc this is not a criticism of your example - not at all - I am
grateful you have made them to help us slow learners.
Anyway thanks for the help and please continue your patient training
and contribution to my education.
respect....
Peter
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden