I fully support this idea since, by definition, an API is a list or
document of function prototypes (or signatures of what have you).
Chad
Sent from an airplane. Shh don't tell anyone.
On May 5, 2009, at 1:17 PM, Mike Lewis <mikelikes...@gmail.com> wrote:
Here's a few other examples to show that this isn't the first time
somebody thought this might be a nice method
http://www.rememberthemilk.com/services/api/methods/rtm.reflection.getMethodInfo.rtm
http://84.234.17.86:84/Tools/API/Method/?name=metaweather.reflection.getMethodInfo
http://developer.etsy.com/docs#getmethodtable
On May 5, 1:46 am, Mike Lewis <mikelikes...@gmail.com> wrote:
Sorry, don't know if the message I just sent got sent or discarded.
In short:
http://github.com/mikelikespie/TwitterLibGen/
data.py
What I'd like the data to be something like. (first 3 at least)
(the rest were scraped and probably are incorrect)
tweetgen.py
Self generating library that uses the data.py info when you
import
it
(play around with it in interactive shell)
test.py
example that uses tweetgen. comment back in the one to see
the auth working (there should be exceptions, it's part of the
demo)
the rest is just the scaper my colleague wrote
On May 4, 1:21 pm, Doug Williams <d...@twitter.com> wrote:
Mike,
That would be great. A good demo can go a long way.
Thanks,
Doug
----------------------------------------------------------------
Doug Williams | Platform Support | Twitter, Inc.
539 Bryant St. Suite 402, San Francisco, CA 94107http://twitter.com/dougw
On Mon, May 4, 2009 at 11:28 AM, Mike Lewis
<mikelikes...@gmail.com> wrote:
Hi Doug,
An example of what I'd be interested in is
http://www.flickr.com/services/api/
flickr.reflection.getMethods.html
and
http://www.flickr.com/services/api/flickr.reflection.getMethodInfo.html
With something like that for the twitter API which shows the
parameters, the request type, if authentication is required, etc.
it
would be very easy to write something that generates a library
for the
API.
It would be able to be very robust because most of the parameter
checking could be done client-side, which means less guessing and
invalid requests to twitter. Also, when there's API changes, the
library could be updated automatically.
Maybe tonight or something, I'll take a couple twitter methods
and put
them in a format similar to what I'd expect, and make a little
demo on
how one could generate a library.
Cheers,
Mike
On May 4, 10:56 am, Doug Williams <d...@twitter.com> wrote:
What we have to offer is available at the wiki. If you have a
great idea
for
something we should add, a working demonstration goes a long way
to
helping
us prioritize.
Thanks,
Doug
----------------------------------------------------------------
Doug Williams | Platform Support | Twitter, Inc.
539 Bryant St. Suite 402, San Francisco, CA 94107
http://twitter.com/dougw
On Mon, May 4, 2009 at 12:16 AM, Mike Lewis
<mikelikes...@gmail.com>
wrote:
I'm asking for the latter. I'm quite familiar with the apiwiki.
On May 3, 11:19 pm, Paul Kinlan <paul.kin...@gmail.com> wrote:
If I am not mistaken, you can look here:
http://apiwiki.twitter.com/Twitter-API-Documentation. That is
unless
you
are asking for programmatic access to an api list via an api?
2009/5/4 Mike Lewis <mikelikes...@gmail.com>
Is there a way to generate a list of API methods in JSON, or
CSV
with
the parameters, or a place where one could download one.
I'm interested in this for generating a library.
Thanks,
Mike
