Re: Documentation frustrations
Re: Documentation frustrations
- Subject: Re: Documentation frustrations
- From: Markus Hitter <email@hidden>
- Date: Tue, 5 Jul 2005 21:36:53 +0200
Am 05.07.2005 um 18:46 schrieb Brandon Sneed:
His [Bills] example of the WindowRef / CreateWindow was a good one.
It was a bad one, because ...
In MSDN for example, one could drill down into the index tree to
the section dubbed "Window Functions",
... in the ADC Ref Lib the terms are "Carbon" -> "User Experience" ->
"Window Manager", which is about the same.
or he could type "CreateWindow" into the search field and the first
result would be the function docs.
Exactly what happens if you do an API search in ADC's documentation
without drilling.
In the docs that come with xcode, if you're in the middle of a
page, click a link, then hit the back arrow, it doesn't take you
back to where you were. You get dumped at the top of a page, and
most of them are pretty long.
Agreed, this is suboptimal. The back/forward buttons should honor mid-
page targets as well. You should file an enhancement request: <http://
developer.apple.com/bugreporter/>.
I figure if Apple wants people to switch, that would include
developers.
It's the same problem as with the end user part of the OS: how would
you explain the experienced Windows user to just forget half of her
knowledge because with Mac OS the function is done in a similar but
different way, or is just obsolete?
Have fun,
Markus
- - - - - - - - - - - - - - - - - - -
Dipl. Ing. Markus Hitter
http://www.jump-ing.de/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden