Hi Joseph,
Thanks for sharing. Perhaps you like to link to your solution from our wiki so others can find it there too? It is also possible to get the xml for 1 todo, i.e. this will work: http://your.server/todos/111.xml In the xml, there is a <state> you can check on active, completed, blocked, etc. Reinier Van: [email protected] [mailto:[email protected]] Namens Joseph Method Verzonden: woensdag 25 januari 2012 2:49 Aan: [email protected] Onderwerp: [Tracks-discuss] Tracks-to-todo.txt plugin Hi all, I built a somewhat Quixotic solution for an extremely limited use case involving Tracks and todo.txt and thought I'd share it in case anyone else is interested. I do my programming using screen and vim directly on the development server at work. At some point I started maintaining a todo.txt file using the todo.txt bash script (todotxt.com). I let it get pretty big and then decided I wanted to be able to synchronize it with my Tracks installation, using the todo.txt plugin system. The silly part is that the development server doesn't have Ruby installed so I developed it in Python. As a by-product I created a Python client library for Tracks, tracks-python. Python isn't the language I usually code in, and the whole project was mainly an exercise in relearning Python. It's not the cleanest code and the setup is complicated, but it works for my needs, and it's nominally TDD. And if you try it and love your data, please back up first. https://github.com/tristil/Todo.txt-Tracks-Sync https://github.com/tristil/tracks-python Also, I ran into a problem implementing this, where it took too long to pull down a large history of /todos/done.xml so I had to guess whether a todo had been completed. What do yinz think about adding a search api? -- -J. Method
_______________________________________________ Tracks-discuss mailing list [email protected] http://lists.rousette.org.uk/mailman/listinfo/tracks-discuss
