API Code Example

[zerok]

I've wrote a little example tool that fetches gaming platforms from Giantbomb and puts them onto a new Dipity timeline. Some unittests are right now in the same file and can be started with the --tests flag.

[econchick]

This looks really good.

Quick request - would you mind separating out the tests from the main file?

Thanks!

[zerok]

Sure :-) hopefully I'll find some time for that this afternoon.

[zerok]

@econchick would you mind if I put the tests into the full_source folder? I'm kind of trying to avoid messing with sys.path within the tests or having to have a wrapper script for manipulating PYTHONPATH :-)

[econchick]

perfectly fine :)

On Fri, Mar 1, 2013 at 8:15 AM, Horst Gutmann notifications@github.comwrote:

@econchick https://github.com/econchick would you mind if I put the tests into the full_source folder? I'm kind of trying to avoid messing with sys.path within the tests or having to have a wrapper script for manipulating PYTHONPATH :-)

— Reply to this email directly or view it on GitHubhttps://github.com/econchick/new-coder/pull/1#issuecomment-14296973 .

[zerok]

OK :-) Then I just have to find out, what changed about the Dipity-API within the last month that breaks my code :-/

[zerok]

OK, it seems like Dipity is broken as a whole for about a week now :-/

https://getsatisfaction.com/dipity/topics/error_adding_event-1g1bab

[econchick]

boooo

what do you think of maybe switching to a different API? Nothing off the top of my head yet but lmk your thoughts

On Mar 1, 2013, at 8:34 AM, Horst Gutmann notifications@github.com wrote:

OK, it seems like Dipity is broken as a whole for about a week now :-/

https://getsatisfaction.com/dipity/topics/error_adding_event-1g1bab

— Reply to this email directly or view it on GitHub.

[zerok]

Yes, that's what I'm planning right now :-) I will keep this pull-request open, if you don't mind, for a little longer in case someone at Dipity notices their "lack" of service, but I will thorugh some ideas around for other implementations.

I kind of still want to use the Giantbomb-API but perhaps with another "output" service :-)

Lynn Root wrote:

boooo

what do you think of maybe switching to a different API? Nothing off the top of my head yet but lmk your thoughts

On Mar 1, 2013, at 8:34 AM, Horst Gutmann notifications@github.com wrote:

OK, it seems like Dipity is broken as a whole for about a week now :-/

https://getsatisfaction.com/dipity/topics/error_adding_event-1g1bab

— Reply to this email directly or view it on GitHub.

— Reply to this email directly or view it on GitHub https://github.com/econchick/new-coder/pull/1#issuecomment-14299588.

[econchick]

I'm fine with the Giantbomb-API - I've actually never heard of it until the script you wrote for it!

I'm hoping to have all the tutorials written by the end of this weekend. I know that puts pressure - and I'm fine if you can't switch out the dipity api.

Let me know your thoughts - right now I've pushed it to the last tutorial that I'll write up.

Last q: are you okay with me giving you credit for coding this part? The tutorials will live on a static site on GitHub pages (probably, maybe heroku, I don't know yet) but it will be public.

[econchick]

AH WAIT I do have one more question - just kidding!

May I ask how you approached this problem? After deciding on the API you wanted to work with, how did you go about structuring your thoughts -> code?

And maybe a bit of final wisdom to impart on new coders? :D

[zerok]

Can't promise it since I'm a little sick right now and off to visiting my parents this weekend, but at least I have another idea for an API example:

1. Again, fetch game platform data from Giantbomb (for all the major TV-based platforms)
2. Fetch CPI data from FRED (not an API but a publically accessible data set)
3. Generate a graph showing the (inflation-adapted) price development of consoles

At first I thought about also adding a Dropbox-share function but I'll doubt I'll get to that.

I guess, the different timezones will work in our favour, though ;-)

Lynn Root wrote:

AH WAIT I do have one more question - just kidding!

May I ask how you approached this problem? After deciding on the API you wanted to work with, how did you go about structuring your thoughts -> code?

And maybe a bit of final wisdom to impart on new coders? :D

— Reply to this email directly or view it on GitHub https://github.com/econchick/new-coder/pull/1#issuecomment-14319838.

[econchick]

Since updated, this one is no longer needed :) Thank you for updating so quickly!