Backend remember the milk

[Lionel Dricot]

http://www.rememberthemilk.com/

[Lionel Dricot (ploum-deactivatedaccount)]

API key (borrowed from tasque) :
b29f7517b6584035d07df3170b80c430

I don't understand all this story of key, frost and token. It seems completely stranger to me. Also, I don't see the point in having an API key as soon as open source software are using one.

There's a python module to connect to RTM, it seems a bit experimental :
http://repo.or.cz/w/pyrtm.git

[LaserJock (laserjock)]

Launchpad developer Tom Berger wrote a python module for RTM. It's at https://launchpad.net/python-rtm . I used it to start a simple CLI interface to RTM. I think it'd really be awesome to use it to get GTG interacting with RTM.

[Keith Hughitt (keith-hughitt)]

I also think this would be a great feature to have. Remember the Milk's API documentation is available here: http://www.rememberthemilk.com/services/api/

More generally, being able to talk to other GTD software and web applications people are already using would be a huge plus.

[Lionel Dricot (ploum-deactivatedaccount)]

We discussed this with Bertrand and we thought that, as none of us is using RTM, it would be better if someone who use it everyday could volunteer to contribute. Of course, we will strongly support any developper that want to create its own backend.

Another problem is that, AFAIK, RTM doesn't suport subtasks. I'm currently working on the backend abstraction so tasks will only have the features of their backend.
It's just a bit sad, IMHO, to use GTG without ever knowing about subtasks because you are using a backend that don't know about them.

[Babyshamble (babyshamble)]

I would like to be a volunteer to test the intregration with RtM. The
problem is that I don't know nothing about programming

On Tue, Mar 10, 2009 at 9:45 AM, Lionel Dricot <email address hidden> wrote:

> We discussed this with Bertrand and we thought that, as none of us is
> using RTM, it would be better if someone who use it everyday could
> volunteer to contribute. Of course, we will strongly support any
> developper that want to create its own backend.
>
> Another problem is that, AFAIK, RTM doesn't suport subtasks. I'm currently
> working on the backend abstraction so tasks will only have the features of
> their backend.
> It's just a bit sad, IMHO, to use GTG without ever knowing about subtasks
> because you are using a backend that don't know about them.
>
> ** Changed in: gtg
> Importance: Medium => Wishlist
>
> --
> Backend remember the milk
> https://bugs.launchpad.net/bugs/320252
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Getting Things Gnome!: Confirmed
>
> Bug description:
> http://www.rememberthemilk.com/
>

--
Economics: ex post rationalization for maintaining current institutional
arrangements.

[tfmoraes (tfmoraes)]

Well, Why not including subtasks as comments? Remember the milk support this. Then it could have a special mark to recognize these comments as subtasks.

[Lionel Dricot (ploum-deactivatedaccount)]

tfmoraes > I don't think it can't work. What about subtasks of subtasks ? What about moving a subtask to another task ?

[tfmoraes (tfmoraes)]

Lionel Dricot, it's a great idea.