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

[Not Zed <notzed ximian com>]

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.

One thing you should do is add a documentation comment for the event.  I have some documentation extraction code which looks for certain headers, and i've been trying to add those where needed, the format may not be finalised, but at least if the code is marked appropriately it can be found later on if it needs changing.

i.e. for the 'message.reading' event, it just has this comment:
        /** @Event: message.reading
         * @Title: Viewing a message
         * @Target: EMEventTargetMessage
         * 
         * message.reading is emitted whenever a user views a message.
         */

The comment needs to start with
"/** @Event: "
all content lines need to start with "* "
and it needs to end with "*/"

doc/devel/build-eplugin-manual.pl has some docbook extraction code in it and needs all of the files listed, but its a bit messy/undocumented, so only try updating that if you're feeling keen (it will need to generate a new xml file and the entity will need to be added to the base document).

Cheers,
 Michael

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.
>
> -David

--

Michael Zucchi <notzed ximian com> "Ride, Work, Sleep. Beer." Novell's Evolution and Free Software Developer