Re: writing an SDK
An SDK is an API with docs, so I guess in a sense if you write
docs for an API then you turn it into an SDK...
An SDK is more than an API with docs. I was going to muster a set of URLs from my favorite online resources, but there's a better way.
Go to Google and ask it
and it will give you a heap of links to definitions that basically agree that an SDK (Software Developers/Development Kit) is code (typically one or more APIs) plus tools (such as an Integrated Development Environment) plus documentation.
--Guy K. Haas
Software Exegete in Silicon Valley
WEBWORKS FINALDRAFT - EDIT AND REVIEW, REDEFINED
Accelerate the document lifecycle with full online discussions and unique feedback-management capabilities. Unlimited, efficient reviews for Word
and FrameMaker authors. Live, online demo:
You are currently subscribed to techwr-l as:
archiver -at- techwr-l -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- techwr-l -dot- com
Send administrative questions to lisa -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/techwhirl/ for more resources and info.
Re: writing an SDK: From: Chris Gooch
Previous by Author:
Anybody got experience doing documentation on compliance with FIPS-140
Next by Author: Re: Menubuilder question in Captivate (formerly RoboDemo)
Previous by Thread: Re: writing an SDK
Next by Thread: Re: writing an SDK
Search our Technical Writing Archives & Magazine