Improved humble bundle imports and button placement

[sir-maniac]

I managed to make imports work through the ajax model objects of the site. The advantages of this, are that the export works for all downloads and keys, no matter which page you are on.

Currently the 'Export to ITAD' exports all downloads and keys in one go. It should be possible to separate this functionality and have 'export keys only', and 'export downloads only' actions.

Humble bundle downloads are sourced as 'humblestore', keys are set to whatever key service is used ('steam', 'origin', 'uplay', etc).

The button is now inserted dynamically for each of the tabs, on both DOM changes and tab clicks. A single button is used and re-inserted in different parts of the DOM in order to be compatible with the caller. =

Let me know if you would like something changed for the merge. Thanks.

[ssokolow]

Hmm. I'm not sure when I'll have time to review this, but I'll leave the tab open as a reminder and try to find time as soon as possible.

(At the moment, I'm still clawing my way back from a huge scheduling mess-up that left me both busy and sleep-deprived enough for my motivation on hobby projects to be somewhat erratic. Given how my impression of CoffeeScript has soured as I became a better developer, I'd hoped to to add automated testing before I poked at this more and then start translating it to TypeScript.)

What I can say is that I'd really prefer if you made it possible to omit keys entirely. The inclusion of keys is a bug that was introduced when Humble redid their library view and I could no longer exclude them with the simple scraping code. (The idea being that the script imports what can actually be downloaded from a given source. If you want to import Steam keys, you go to Steam.)