Re: Sending "content-changed" signal on store/remove?

[Iago Toral Quiroga <itoral igalia com>]

Agreed.

Actually, notice that when you store content, the plugin may not need to
signal content-changed inmediately. Very likely it will do that
naturally when the backend where it is actually storing the content
signals the change, just as if the content were stored through other
means.

In cases where the backends do not support this, like in our bookmarks
plugins, the plugin itself could add specific code to emit the signal
upon successful execution of the store() method.

So, as Guillaume says, I think plugins should handle this, and do that
in the way that makes sense for them.

Iago

El vie, 04-02-2011 a las 12:01 +0100, Guillaume Emont escribió:
> I think that it should send the signal as well, that _is_ a content change.
> Also, I feel it should be the plugin's responsibility to do that, not
> the core's.
> 
> Guij
> 
> On 04/02/2011 11:52, Juan A. Suárez Romero wrote:
> > Hello.
> >
> > I would like to hear your opinions here.
> >
> > Should a source that supports store() and/or remove() operations send
> > "content-changed" signal when someone stores or remove content?
> >
> > My opinion is that it should, but I would like to hear your opinions
> > too.
> >
> > 	J.A.
> >
> >
> > _______________________________________________
> > grilo-list mailing list
> > grilo-list gnome org
> > http://mail.gnome.org/mailman/listinfo/grilo-list
> >
> 
> _______________________________________________
> grilo-list mailing list
> grilo-list gnome org
> http://mail.gnome.org/mailman/listinfo/grilo-list
>