gtg-user team mailing list archive

["Lionel Dricot" <ploum@xxxxxxxxx>]

Hi luca,


There's one thing that makes me unconfortable in your proposition : we
originally planned backends for tasks to be completely differents than
plugins.

I believe that supporting multiple backends has to be thought carefully.
If you read the localfile.py backend, you will see that backends were
really abstracted and are generic.

Actually, GTG already support multiple backends, there's simply no UI for
them and some issue likes "how to assign a given task to one of your
backend" and some other oddities.

But maybe I'm wrong and adding multiple backends via plugin is the way to go.

So, the wise way would be to wait that multi-backends support is properly
finished. But is being wise always needed ?

I really don't know


Lionel

> Developers^3, hi.
> Seeing Paulo plugins-engine, I've decided to write a plugin for
> synchronizing gtg with Remember the milk (www.rememberthemilk.com, you
> have a blueprint for that). Currently, I'm in the phase where I can get
> both
> lists of tasks, and I'm deciding how to merge them.
> Since RTM:
> - does not have subtask
> - does not have start date
> - has a task description that is very similar to gtg
>     task title (they support multiple notes per task, however),
>
> it's not so trivial to me to see the best way to sync.
> Up to now, my best idea is maintaining a table of GTG_TID <->RTM_TID.
>
>
> Moreover, I'll need to store some data (namely, RTM api auth token):
>     how should I do that to integrate smoothly with gtg architecture?
>     Some kind of ~/.config/gtg/plugins/$PLUGIN_NAME directory?
>
> Thanks in advance (and for the awesome work),
>
>        Luca Invernizzi
>
> _______________________________________________
> Mailing list: https://launchpad.net/~gtg
> Post to     : gtg@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~gtg
> More help   : https://help.launchpad.net/ListHelp
>