Re: Which DocSets to Get?
Re: Which DocSets to Get?
- Subject: Re: Which DocSets to Get?
- From: Ronald Hayden <email@hidden>
- Date: Mon, 21 Sep 2009 16:49:52 -0700
This is apparently not the case. I had to tell Xcode to "get" the
10.6 core and iPhone 3.x doc sets. IIRC, only the Xcode tools doc
set was pre-installed.
If during the install process you didn't turn off the "Documentation"
option in the Installer, we don't know how a person could get into
this state, since there shouldn't be any current way to install Xcode
without at least the doc set for one SDK being installed along with
it. If you could file a bug that indicates the steps you took to
install or upgrade Xcode, that would help. Sometimes there are
upgrade paths that can cause unexpected behavior.
-- Ron
On Sep 21, 2009, at 4:17 PM, Keary Suska wrote:
On Sep 21, 2009, at 4:28 PM, Ronald Hayden wrote:
With Xcode 3.2, how does one determine which documentation sets
should be downloaded?
By default, you should have any current documentation relevant to
the installed SDKs.
If your preference is set to auto-download doc updates (which is
the default for new users, but long-time users may have different
settings), and you only need the current docs relevant to the SDKs
you are using, you shouldn't have to do anything.
This is apparently not the case. I had to tell Xcode to "get" the
10.6 core and iPhone 3.x doc sets. IIRC, only the Xcode tools doc
set was pre-installed.
The design of the doc system in Snow Leopard is to make it such
that the typical Xcode user should never have to think about what
docs they need or whether to update the docs -- the "right thing"
should happen automatically.
This would be nice.
Do all the "newer" sets (e.g. 10.6 vs 10.5, iphone 3 vs 2.x, etc)
include all legacy info, or may there be important information
excluded in these "newer" sets?
As of Snow Leopard, legacy docs are no longer part of the standard
RefLibs, to address long-standing concerns of search results being
cluttered with legacy docs. If you need the legacy OS X
documentation, you can go into the Documentation pref pane and
"Get" the OS X Legacy RefLib. At this time only the OS X docs have
a legacy RefLib; in the future, as appropriate, we'll add Legacy
doc sets for other platforms (web/iPhone).
Note that "Legacy" here refers to complete documents that have been
consigned to legacy. Legacy API will still be reflected in the
regular RefLib, in a separate file for the class, as has been the
case for a few years.
There should be no "important" information in the Legacy RefLib,
unless by mistake. If it's important to current development, it
remains in the regular RefLib.
I assume that "legacy" means "officially deprecated", in which case
this sounds good.
Thanks for the clarification.
Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"
_______________________________________________
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