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.

This was written by Lawrence. Posted on Tuesday, December 22, 2009, at 11:49 am. Filed under Everything. Tagged , , , , , , , . Bookmark the permalink. Follow comments here with the RSS feed. Both comments and trackbacks are currently closed.

24 Comments 1 Tweet

31 Comments

  1. Lawrence Oluyede wrote:

    shameless plug per dimostrare quanto e` figo Git e per dirvi che ho riscritto Pinder nel caso vogliate usare Campfire da Python :-) (ai tempi lo avevo scritto per integrare le chatroom da un sito web)

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 11:52 am | Permalink
  2. Lawrence Oluyede wrote:

    ovviamente il feedback e` BENVENUTISSIMO

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 11:52 am | Permalink
  3. Michele Campeotto wrote:

    non uso Campfire quindi non so, ma credo che con l’estensione giusta al nome del file github prenda anche la formattazione del README.

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 12:44 pm | Permalink
  4. Lawrence Oluyede wrote:

    la formattazione restructuredText? Mmm non saprei, il wiki supporta Textile. Mi informo

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 12:45 pm | Permalink
  5. Michele Campeotto wrote:

    di sicuro ho visto progetti con Markdown, non so rst.

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 12:48 pm | Permalink
  6. Michele Campeotto wrote:

    ho visto progetti anche con Markdown, non so rst.

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 12:48 pm | Permalink
  7. Lawrence Oluyede wrote:

    Ecco: http://github.com/guides/readme-formatting

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 12:52 pm | Permalink
  8. Lawrence Oluyede wrote:

    Ha decisamente funzionato http://github.com/rhymes/pinde...../usage.rst

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 12:59 pm | Permalink
  9. Michele Campeotto wrote:

    rocchenroll.

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 1:58 pm | Permalink
  10. Folletto Malefico wrote:

    Ok, quindi anche tu GIT eh? :P

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:44 pm | Permalink
  11. Lawrence Oluyede wrote:

    decisamente. durante le (non) vacanze di Natale provo a preparare delle motivazioni per convincere il team a fare lo switch (o linko loro http://whygitisbetterthanx.com/)

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:52 pm | Permalink
  12. Alan Franzoni wrote:

    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.

    Tuesday, December 22, 2009 at 4:53 pm | Permalink
  13. Timothy Redaelli wrote:

    occhio a passare a git da svn, controlla se non hai directory vuote che ti servono…

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:53 pm | Permalink
  14. margotta wrote:

    qua lo usano e io ogni volta non mi ricordo come si fa il repository :S

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:53 pm | Permalink
  15. Folletto Malefico wrote:

    Io avevo iniziato con git dopo un po’ di dubbi, poi ho un po’ considerato hg per la facilità di tirare su un server ad-hoc per lo scambio in P2P in rete locale (che trovo comodissimo, non capisco perché sia così complicato). Ora mi sa però che torno su git…

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:54 pm | Permalink
  16. Lawrence Oluyede wrote:

    @Timothy: terro` a mente, noi abbiamo un repository di 1.2 Gigabyte -_-. C’e` dentro di tutto @Folletto: in effetti quel vantaggio non e` trascurabile

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:56 pm | Permalink
  17. Folletto Malefico wrote:

    Puoi farlo anche con git eh, solo che l’ultima volta che avevo provato – un paio di mesi fa – era leggermente più complicato, anche se poi con hg c’erano casini di gestione permessi scrittura (ma zio bon, se IO tiro su esplicitamente un server ad-hoc, significa che voglio farci scrivere no? :D ) :D

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 4:58 pm | Permalink
  18. Lawrence Oluyede wrote:

    Ho appena trovato questo http://github.com/chad/gitjour

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:03 pm | Permalink
  19. Folletto Malefico wrote:

    Mica male, ci do un occhio (bello il setup che usa gem! :D ). :P L’altro problema cmq sono le GUI, ho purtroppo utenti windows che sono abituati a Tortoise e le app Windows per GIT sono ancora un po’ troppo embrionali — Te lo dico che magari hai già una soluzione :D :)

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:04 pm | Permalink
  20. Folletto Malefico wrote:

    Mica male, ci do un occhio. :P L’altro problema cmq sono le GUI, ho purtroppo utenti windows che sono abituati a Tortoise e le app Windows per GIT sono ancora un po’ troppo embrionali — Te lo dico che magari hai già una soluzione :D :)

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:04 pm | Permalink
  21. Lawrence Oluyede wrote:

    No, sono rimasto a questo http://code.google.com/p/tortoisegit/

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:05 pm | Permalink
  22. Lawrence Oluyede wrote:

    Tra l’altro per noi Windows e` una discriminante, se il tool non funziona perfettamente anche li` direi che non si puo` fare lo switch :D

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:05 pm | Permalink
  23. Folletto Malefico wrote:

    Ottimo, quindi siamo nella stessa situazione :P

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:07 pm | Permalink
  24. Folletto Malefico wrote:

    Si, quei comandi alla fine li avevo trovati, sarebbe meglio un bel default efficace ma ci accontentiamo. :P

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:08 pm | Permalink
  25. Michele Campeotto wrote:

    devo dire che la staging area è cosa molto fica.

    This comment was originally posted on FriendFeed

    Tuesday, December 22, 2009 at 5:21 pm | Permalink
  26. Orestis Markou wrote:

    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!

    Tuesday, December 22, 2009 at 7:32 pm | Permalink
  27. Luca Matteis wrote:

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

    Tuesday, December 22, 2009 at 11:55 pm | Permalink
  28. Lawrence wrote:

    @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

    Wednesday, December 23, 2009 at 2:43 am | Permalink
  29. Lawrence wrote:

    @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?

    Wednesday, December 23, 2009 at 2:46 am | Permalink
  30. Lawrence wrote:

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

    Bye!

    Wednesday, December 23, 2009 at 2:47 am | Permalink

One Trackback/Pingback

  1. uberVU - social comments on Tuesday, December 22, 2009 at 12:49 pm

    Social comments and analytics for this post…

    This post was mentioned on Twitter by lawrenceoluyede: #Pinder, take two http://goo.gl/fb/IS9j #everything #api #campfire #chat #git #github #json #python…

Additional comments powered by BackType