A friend pointed me to a *really* interesting documentation browser with
features along these lines. (Classes and methods have their own wiki pages is
what reminded me of this old thread on cocoa-dev, but there's lots more.) I've
only played with it a bit, but it seems very sharp and
On 23 May 2008, at 01:38, [EMAIL PROTECTED] wrote:
On May 22, 2008, at 11:15 AM, Jonathan Hendry wrote:
Perhaps a better way of doing this would be a web or WebKit app with
two panes. One that shows the Apple docs at Apple's site, and the
other pane points to a page at a non-Apple wiki site
On May 23, 2008, at 2:23 AM, Gerriet M. Denkmann wrote:
1. For me the documentation would be very hard to use without the
excellent AppKiDo.
2. It really should be Apple's job to provide something like AppKiDo.
There is new browsing facilities in Xcode 3.0. Research Assistant,
and
On 22 May 2008, at 23:19, Scott Anguish wrote:
On May 22, 2008, at 10:39 AM, Julius Guzy wrote:
On 22 May 2008, at 4:55, David Casseres wrote:
That's a really good idea, your wiki-that's-more-than-a-wiki.
You're in charge!
8^{)
Ha Ha
But just as a matter of interest, how would one
On 23 May 2008, at 11:49, Ken Thomases wrote:
On May 23, 2008, at 3:09 AM, Gerriet M. Denkmann wrote:
I do seem to remember that there was something to write files and
folders to a CDs using an Objective-C interface.
- entered disk into AppKido - nothing except NSURLCache.
- entered disk
The documentation is for the most part oriented around the
implementation of the technologies offered (inside out view) rather
than the solving of the challenged faced (outside in view). For
experts this is no great barrier, because they are already arguably
inside. But see how this
On 22 May 2008, at 4:55, David Casseres wrote:
That's a really good idea, your wiki-that's-more-than-a-wiki.
You're in charge!
8^{)
Ha Ha
But just as a matter of interest, how would one set about talking to
apple about such a thing?
I would guess one would need first to demonstrate some
Perhaps a better way of doing this would be a web or WebKit app with
two panes. One that shows the Apple docs at Apple's site, and the
other pane points to a page at a non-Apple wiki site that corresponds
to the currently displayed Apple site.
That would ensure that the Apple content stays
On May 22, 2008, at 10:39 AM, Julius Guzy wrote:
On 22 May 2008, at 4:55, David Casseres wrote:
That's a really good idea, your wiki-that's-more-than-a-wiki.
You're in charge!
8^{)
Ha Ha
But just as a matter of interest, how would one set about talking to
apple about such a thing?
I
On May 22, 2008, at 11:15 AM, Jonathan Hendry wrote:
Perhaps a better way of doing this would be a web or WebKit app with
two panes. One that shows the Apple docs at Apple's site, and the
other pane points to a page at a non-Apple wiki site that
corresponds to the currently displayed
That's a really good idea, your wiki-that's-more-than-a-wiki.
You're in charge!
8^{)
On May 19, 2008, at 5:31 AM, Julius Guzy wrote:
Well I never thought I would cause this much discussion.
I have tried but do not have the time needed to reply to all.
I might still but work must take
Well I never thought I would cause this much discussion.
I have tried but do not have the time needed to reply to all.
I might still but work must take precedence.
There have been a number of people who suggested I give specific
instances of documentation failure.
I agree it would be useful
12 matches
Mail list logo
