I feel like there was a nice bit of miscommunication back there. Hopefully this will clear up what I was asking for. Bug #507365<https://bugs.launchpad.net/do/+bug/507365> .
--Ashton On Thu, Jan 14, 2010 at 3:09 AM, Ashton Kemerling <[email protected] > wrote: > That's exactly what I want. My plugin never needs a refresh until the user > performs some action (the plugin is notified via DBus), then a re-index is > required. I think all we are looking for is an API call for plugins to > request a refresh. Perhaps we could even set it so that a plugin could > control whether or not it recieves periodic, automatic, refreshes. > > Hopefully I'm being clear enough. > > --Ashton > > On Thu, Jan 14, 2010 at 3:02 AM, Chris Szikszoy > <[email protected]>wrote: > >> On Wed, Jan 13, 2010 at 11:41 PM, Ashton Alan Kemerling >> <[email protected]> wrote: >> > Perhaps we can put it in the roadmap to 1.1 then? >> >> Please read my comments on the bug report, but the short of it is this >> won't happen. With a properly designed plugin api (and plugins that >> properly make use of it) there should be absolutely no need for a user >> to initiate a reindex or refresh of Do's items. Plugins should be >> state aware, and aware of the items they own, and therefore should be >> responsible for signaling Do that a refresh should happen. >> >> - Chris S. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "GNOME Do" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<gnome-do%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/gnome-do?hl=en. >> >> >> >> >--
You received this message because you are subscribed to the Google Groups "GNOME Do" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected].
For more options, visit this group at http://groups.google.com/group/gnome-do?hl=en.
