gtg-user team mailing list archive

[Duncan Lock <dunc@xxxxxxxxxxxx>]

I would think that pluggable backends would be the way to go, from and end
user point-of-view at least. Not sure how this would work from a programming
perspective, but I would definitely prefer it as a user.
Dunc

2009/8/5 Bertrand Rousseau <bertrand.rousseau@xxxxxxxxx>

> Coudn't we add backends by using plugins? That would be an interesting
> feature.
>
> I guess we always thought of providing GTG with built-in backends for
> sync with several task managers, but we never thought as them as being
> activable plugins. Having some backends as default feature is nice,
> but what if it starts to add weird dependencies? Plugin backends could
> have some advantages.
>
> Actually, I don't know what the best is either.
>
> Bertrand
>
> On Tue, Aug 4, 2009 at 5:07 PM, Lionel Dricot<ploum@xxxxxxxxx> 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
> >>
> >
> >
> >
> > _______________________________________________
> > Mailing list: https://launchpad.net/~gtg-user
> > Post to     : gtg-user@xxxxxxxxxxxxxxxxxxx
> > Unsubscribe : https://launchpad.net/~gtg-user
> > More help   : https://help.launchpad.net/ListHelp
> >
>
>
>
> --
> Bertrand Rousseau
> Place communale 1, 1450 Chastre, Belgium
> e-mail : bertrand.rousseau@xxxxxxxxx
> tel : +32 485 96 69 86
>
> _______________________________________________
> Mailing list: https://launchpad.net/~gtg-user
> Post to     : gtg-user@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~gtg-user
> More help   : https://help.launchpad.net/ListHelp
>
>