Skip to content

Pinder, take two

Pinder is my Python client for the 37 Signals’s Campfire online chat.

With the excuse of learning Git (by the way GitHub is awesome!) I rewrote it from scratch following the official Campfire API.

Needless to say that it took me very little time. Git is damn fast, Python development is already fast, JSON is basically a standard and the API is easy and clean. I bumped into a couple of problems but I am confident they’ll be fixed soon.

You can find Pinder on my GitHub page.

Next year I’ll try to present a case here at the company I work to switch from Subversion to either Git or Mercurial.

Share and Enjoy:
  • Print
  • Digg
  • StumbleUpon
  • Facebook
  • Twitter
  • Google Bookmarks
  • FriendFeed
  • Google Buzz
  • HackerNews
  • Posterous
  • Reddit
  • Slashdot
  • Tumblr
  • Pingback: uberVU - social comments

  • http://www.franzoni.eu Alan Franzoni

    I think that if Windows support is needed at your company, it’s quite hard to migrate to git – the native client is still in a beta version, and the GUI is pretty rough.

    Combine that with the fact the tool is still pretty complex if compared with mercurial or svn and you have a perfect showstopper.

  • http://orestis.gr Orestis Markou

    re: Pinder – nice, I guess defunkt’s and mine forks are obsolete now (or we should just test the new repo to see if it satisfies our needs). Will let you know!

    re: git – the msysgit client is pretty stable, and the GUI is more than adequate (even though it looks ugly). Give it a go to see if it fits your needs!

  • http://pseudocodice.com Luca Matteis

    Apart from local history backup I don’t understand the reason of using git.

  • http://www.oluyede.org/blog/ Lawrence

    @Alan: yeah, Windows support is the main drawback. But it’s not still true that Git is difficult. I learn it in a half hour reading http://learn.github.com

    The documentation is excellent.

    It’s true that it has more features, but it’s not that difficult, at least for my current use cases (lone development and merge of forks).

    You can go very far with just commit, add, checkout, pull, push, mv and merge

  • http://www.oluyede.org/blog/ Lawrence

    @Orestis. Hi there! The fork is not that obsolete, the problem is that tracking down continous changes of Campfire HTML layout is not the best thing in the world. I noticed they released an official API and I rewrote it. I still have to implement room creation (which oddly does not work even with curl), upload and streaming and that’s it.

    Let me know!

    ps. I will definitely look at msysgit. What about tortoise-git? Have you ever tried it?

  • http://www.oluyede.org/blog/ Lawrence

    @Luca: eh eh :-) here you can find some reason to use Git or distributed source control systems in general: http://whygitisbetterthanx.com/

    Bye!