Re: Working With Conduit

On 11/30/07, D Bera <[email protected]> wrote:
>
> Hi,
>
> > Was just speaking to kkubasik on #tomboy about scope for work between
> > conduit [1] and beagle.
> >
> > To cut a long e-mail short: Conduit syncs things in both directions.
> Data
> > thing goes in, data thing comes out. So we have a growing range of
> plugins
> > for different applications, web services and devices. My idea is: If we
> get
> > data out, why can't we fire it to beagle too. Kill two birds with one
> stone.
>
> Which two birds ? I mean, I don't understand the goal here. From the
> link in your email, I understand conduit is a synchronization program
> for user data across machines. Roughly, at least. So where does beagle
> do in this picture ? Can you elaborate on that a little ?
>
> Thanks,
> - dBera


It's quite simple really. What does a beagle indexer do? It gets data out of
an application, puts it into a format it understands and fires it at the
index. What does a Conduit plugin do? One part is getting data out of an
application, putting into a format the sync engine understands and fire it
at the sync engine. What i'm offering is the ability to index data from any
source that conduit supports as a sync source.

KKubasik was also interested in the mapping data - "oh, this photo came from
flickr account "foo bar", and this one from a digital camera".

Hope that makes more sense!
John

_______________________________________________
Dashboard-hackers mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/dashboard-hackers