specifying what services Activities may use
eben.eliason at gmail.com
Wed Jul 30 11:12:28 EDT 2008
On Wed, Jul 30, 2008 at 11:03 AM, Greg Smith <gregsmitholpc at gmail.com>wrote:
> Hi Daniel,
> What I think we need is a list of all APIs relevant to activity
> developers (maybe libraries too?). You can parse it however you want.
The two resources we do have, that I know of, are:
Neither, it seems, is complete, but I think they are being actively worked
on. I think our ability to adequately predict and/or prevent breakage will
improve quite a bit over the next few releases, when a) APIs are better
documented in the first place (which also gives us obvious places to
indicate future changes, additions, and deprecations) and b) fewer pieces of
the system need to change at once, lowering the number of variables
> We need a list of anything that might "break" an activity. Give us
> whatever you have, even if its not the full story. Hopefully we can put
> together the full puzzle one piece at a time.
> Greg S
> Daniel Drake wrote:
> > On Wed, 2008-07-30 at 07:02 -0400, Greg Smith wrote:
> >> Michael and team,
> >> Can we get documentation of all API changes (since 708 and 656) that
> >> affect activities ASAP?
> > Are you talking about sugar APIs, or APIs for other library components
> > present on the system which some activities may use?
> >> BTW where is the definitive documentation of all APIs available to
> >> activities and is it up to date?
> >> When can we freeze API changes for 8.2.0?
> > Again, same question for both. Sorry to answer a question with a
> > question :)
> > Daniel
> Devel mailing list
> Devel at lists.laptop.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Devel