Re: [evolution-patches] "component.migration" event for calendar component

[JP Rosevear <jpr novell com>]

On Wed, 2005-01-05 at 09:20 +0800, Not Zed wrote:
> 
> I guess it'll do.  It could perhaps have migration version information
> in the event, but I guess it doesn't matter too much/could be done
> later.
> 
> On Tue, 2005-01-04 at 00:49 -0700, David Trowbridge wrote: 
> > Ok, here's the updated version with the comment, documentation builder
> > entry and changelog. I've tried to explain in the comment the reasoning
> > behind this event.
> > 
> > -David
> > 
> > On Tue, 2005-01-04 at 11:09 +0800, Not Zed wrote:
> > > 
> > > Looks fine.  Seems a bizarre thing to need an event for though.
> > > Should it just be a component-started event?  But maybe there's other
> > > reasons for it, so i'm just speculating.
> > > 
> > > On Mon, 2005-01-03 at 15:36 -0700, David Trowbridge wrote: 
> > > > This adds a new event that is triggered at the calendar migration step
> > > > (which occurs every time evolution starts). This allows plugins to
> > > > supply their own source groups.

It should not be occuring every time evolution starts iirc.  Only when
the version changes.

Perhaps the startup event should be used instead?  Also does this handle
disabling the plugin and having the groups go away at all?

-JP
-- 
JP Rosevear <jpr novell com>
Novell, Inc.