Getting Things GNOME! — GSoC review (#2)


Aloha again, planet Gnome!
This has been a nice week for my Google Sum­mer of Code project on Get­ting Things GNOME, fea­tur­ing:

  • A great speedup (via the refac­tor­ing of how the file con­tain­ing all the tasks is han­dled): the time for adding 1000 tasks in GTG has been reduced from 30 to 5 seconds!
  • A new test­ing class, which helped me find-n-fix a few bugs (ehi! test­ing works!)
  • The first request to merge of part of my code  (~3600 lines). I have to thank my men­tor Lionel Dri­cot, who has found the time to go through it.
  • A new twit­ter back­end. It still misses the UI to con­fig­ure the user­name and pass­word, but the basic func­tion­al­ity is there. Cur­rently, it adds to GTG any direct mes­sage match­ing a set of cho­sen tags (e.g., #todo).

I’m still work­ing on twit­ter authen­ti­ca­tion. I’m cur­rently doing it via the userid/password combo, but the cor­rect way to go should be Oauth. Unfor­tu­nately, python-twitter does not sup­port this. I’ve found a few libraries around the web, but none seem to work so far. Any hint  will be welcome.

Next week I’m plan­ning to fin­ish the twit­ter back­end, expand­ing the frame­work as I go. A nice thing is that, thanks to the frame­work, the twit­ter back­end (which is all a devel­oper should write to add a new back­end) is less than 100 lines long.

  • http://the-gay-bar.com tante

    tweepy is a great library to work with Twit­ter from Python, but oauth has a bunch of prob­lems for open source apps (you have to ship your secret keys with the app mean­ing that your keys can be used by oth­ers to scam peo­ple into giv­ing untrusted peo­ple access to their pro­file. There is Xauth which is bet­ter but you have to get your app accepted for that man­u­ally (there’s no auto­matic process). The Tweepy docs have a bunch of exam­ples on how stuff works.

  • http://the-gay-bar.com tante

    tweepy is a great library to work with Twit­ter from Python, but oauth has a bunch of prob­lems for open source apps (you have to ship your secret keys with the app mean­ing that your keys can be used by oth­ers to scam peo­ple into giv­ing untrusted peo­ple access to their pro­file. There is Xauth which is bet­ter but you have to get your app accepted for that man­u­ally (there’s no auto­matic process). The Tweepy docs have a bunch of exam­ples on how stuff works.

  • http://www.lucainvernizzi.net Luca Inv­ernizzi

    Thanks for that!

  • http://www.lucainvernizzi.net Luca Inv­ernizzi

    Thanks for that!

  • guest

    Please con­sider adding Sta­tus­Net sup­port too, it has a Twit­ter com­pat­i­ble API, shouldn’t be too dif­fi­cult to implement.

  • guest

    Please con­sider adding Sta­tus­Net sup­port too, it has a Twit­ter com­pat­i­ble API, shouldn’t be too dif­fi­cult to implement.

  • http://www.lucainvernizzi.net Luca Inv­ernizzi

    Sure!

  • http://www.lucainvernizzi.net Luca Inv­ernizzi

    Sure!

Getting Things GNOME! — GSoC review (#2)


Aloha again, planet Gnome!
This has been a nice week for my Google Sum­mer of Code project on Get­ting Things GNOME, fea­tur­ing:

  • A great speedup (via the refac­tor­ing of how the file con­tain­ing all the tasks is han­dled): the time for adding 1000 tasks in GTG has been reduced from 30 to 5 seconds!
  • A new test­ing class, which helped me find-n-fix a few bugs (ehi! test­ing works!)
  • The first request to merge of part of my code  (~3600 lines). I have to thank my men­tor Lionel Dri­cot, who has found the time to go through it.
  • A new twit­ter back­end. It still misses the UI to con­fig­ure the user­name and pass­word, but the basic func­tion­al­ity is there. Cur­rently, it adds to GTG any direct mes­sage match­ing a set of cho­sen tags (e.g., #todo).

I’m still work­ing on twit­ter authen­ti­ca­tion. I’m cur­rently doing it via the userid/password combo, but the cor­rect way to go should be Oauth. Unfor­tu­nately, python-twitter does not sup­port this. I’ve found a few libraries around the web, but none seem to work so far. Any hint  will be welcome.

Next week I’m plan­ning to fin­ish the twit­ter back­end, expand­ing the frame­work as I go. A nice thing is that, thanks to the frame­work, the twit­ter back­end (which is all a devel­oper should write to add a new back­end) is less than 100 lines long.