FROM : Andy Lee
DATE : Thu May 15 03:29:05 2008
On May 14, 2008, at 9:15 PM, I. Savant wrote:
> On May 14, 2008, at 9:06 PM, Andy Lee wrote:
>
>> It can be a little tricky to find, though.
>
> That's only if you're searching myopically for that one answer.
Or if you're trying to tell someone where he would have found the
answer if he'd read the conceptual documentation methodically. :)
Fair point, and the distinction between concepts docs and API
reference is an important one.
--Andy
> If, on the other hand, you read the conceptual documentation all the
> way through as you're meant to, you should definitely come across it
> in context and in a reasonably good order.
>
> As the author of AppKiDo, I know you understand the importance of
> effective research, so I'm not being dismissive. I say that because
> this really is more of a conceptual topic and that's exactly why the
> conceptual documentation is there. It's meant to be consumed first
> (chew thoroughly), then referenced later. Contrast with the API
> reference, which really is meant for just that.
>
> --
> I.S.
>
>
>
DATE : Thu May 15 03:29:05 2008
On May 14, 2008, at 9:15 PM, I. Savant wrote:
> On May 14, 2008, at 9:06 PM, Andy Lee wrote:
>
>> It can be a little tricky to find, though.
>
> That's only if you're searching myopically for that one answer.
Or if you're trying to tell someone where he would have found the
answer if he'd read the conceptual documentation methodically. :)
Fair point, and the distinction between concepts docs and API
reference is an important one.
--Andy
> If, on the other hand, you read the conceptual documentation all the
> way through as you're meant to, you should definitely come across it
> in context and in a reasonably good order.
>
> As the author of AppKiDo, I know you understand the importance of
> effective research, so I'm not being dismissive. I say that because
> this really is more of a conceptual topic and that's exactly why the
> conceptual documentation is there. It's meant to be consumed first
> (chew thoroughly), then referenced later. Contrast with the API
> reference, which really is meant for just that.
>
> --
> I.S.
>
>
>






Cocoa mail archive

