On Jul 17, 2008, at 1:05 PM, John Love wrote:
... and the lights went on ... and I hear fireworks!
Andy said I think of each of those bunches as categories of methods.
I'm glad it was good for you. :)
--Andy
___
Cocoa-dev mailing list
Well, you seem to be happy so far be it from me to spoil your mood...
But this makes very little sense to me.
What delegate chain? Do you mean responder chain? The responder
chain (if that *is* what you're referring to) is not an example of the
delegate pattern, it's an example of the chain
As some of you realize, I have a fetish about compartimentalization, that
is, the making of separate files(.h,.m) as much as possible ... and I
erroneously concluded that the only way to do that was via the construction
of multiple Controllers within IB. It turns out that that is one means when
I should be careful about claiming what I told you and then posting
code that definitely did *NOT* come from me.
What on earth is a delegator? Do you mean 'delegate'? I believe that
is the terminology I used, and with good reason - it's the normal
jargon for this design pattern (not just
On Jul 15, 2008, at 9:13 AM, John Love wrote:
To tell you the truth, I *really* prefer calling a category an
extension
because extension just sounds more meaningful to me. Or, maybe just
plain, ole, generic addition. Category just sounds like type
of or a
sub-class, but it's not that at
Well, what are you asking? Does the code work or not? If not, what are the
symptoms?
Yes, it works without a shred of doubt .. I'm just trying to get my hands
around Category .. there is no doubt whatsoever that unless I use
Category, no one will know what I'm talking about .. it just would be
On Tue, Jul 15, 2008 at 2:01 PM, John Love [EMAIL PROTECTED] wrote:
Programmers are rarely accused of using plain English all the time,
anyway.
In fact we're notorious for redefining already well-defined words.
That's the fun of English; there is only usage, which makes it a very
ambiguous yet
On Jul 15, 2008, at 2:01 PM, John Love wrote:
it just would be nice
if Cocoa's Category would meld with Merriam Webster's definition of
category .. probably too much to ask.
It does. Did you see my earlier reply?
Programmers are rarely accused of using plain English all the time,
anyway.
Uli -
To enable/disable the toolbar items, Cocoa uses the
NSUserInterfaceValidation protocol, and asks each responder in the responder
chain, beginning at the first responder. Have you inserted your toolbar
controller in the responder chain so it actually gets asked whether these
methods should
On 8 Jul 2008, at 12:13 am, John Love wrote:
Initially, my ToolbarController was sub to NSObject as was the case
for
Apple's SimpleToolbar, so I changed the super class of my
ToolbarController
to NSControl.
Huh? This makes no sense whatsoever. Why not just make your toolbar's
Apple's SimpleToolbar code *is all* their MyDocument.m. My app would like
to place the toolbar-specific code *in a separate Controller*, say
ToolbarController. This transfer does work to a limited extent, that is,
the toolbar does in fact appear at the top of the window, as it should.
However,
On 05.07.2008, at 21:05, John Love wrote:
Apple's SimpleToolbar code *is all* their MyDocument.m. My app
would like
to place the toolbar-specific code *in a separate Controller*, say
ToolbarController. This transfer does work to a limited extent,
that is,
the toolbar does in fact appear
12 matches
Mail list logo
