Re: Re: writing an SDK

Subject: Re: Re: writing an SDK
From: Susan W. Gallagher <sgallagher5 -at- cox -dot- net>
To: "TECHWR-L" <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Wed, 13 Apr 2005 17:27:10 -0400

I've worked in a lot of companies that sold code.
To some, an API was developed "ready to use" and an SDK had
to be compiled on the user-dev's machine. To some, an SDK
was specifically meant to extend another commercial application
(like an SDK for Word so you could develop RoboHelp) and
everything else was an API. To some, each individual method
is an API (eww, I hate this one) and SDK never even enters
the vocabulary. This "documentation magically turns an API
into an SDK" definition is a new one on me, but that doesn't
mean it isn't valid *somewhere*. <g>

Whether it's called an API or an SDK, the task is essentially
the same -- helping the user-dev integrate the supplied
code into an application.

A rose by any other name... and all that.

-Sue Gallagher


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 for more resources and info.


Previous by Author: Re: writing an SDK
Next by Author: Re: Books on developing survey questions
Previous by Thread: Re: writing an SDK
Next by Thread: RE: Re: writing an SDK

What this post helpful? Share it with friends and colleagues:

Sponsored Ads