gtg team mailing list archive

[Luca Invernizzi <invernizzi.l@xxxxxxxxx>]

Hi Lionel,
   I think that this plugin can be easily converted in a backend, since
   it makes only a couple of calls to the plugins api.
   But I'm not so sure of using RTM as a backend, since it does not support many
   things that GTG implements (like subtasks).
   Moreover, for what I've understood (I've read only a small subset of
    the code), backends are constantly called in GTG activity. Most web
   services, however, apply rate limitations to their API calls (for
    RTM, it's 1 call per second maximum).
   Because of that, and because internet connections can be very
   unreliable at times, the RTM backend would need a local cache of
   changes to be applied (which is very similar to a localfile backend).

   I thought that the RTM plugin would synchronize only once in a while
   GTG with RTM, and only the data that are in the intersection of the
   two services (plus some workarounds - e.g: for subtasks ).

   But, of course, I've been looking at this code only for the last
   four days and in my spare time, so you all will know best what to do.

   Luca

On Tue, Aug 04, 2009 at 05:07:47PM +0200, Lionel Dricot wrote:
> 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
> >
> 
>

Attachment: signature.asc
Description: Digital signature