Re: [Evolution-hackers] camel eds work progress




> Worse, stuff from eds/servers/ which must be built after camel anyway.
> 
I wonder if the groupwise provider could just continue in evolution, as
an extension plugin to libcamel.
Well now that plugins have an ability to 'load on startup', they could register camel plugins directly from in-memory objects rather than doing it from the camel provider dir.

But i don't like this solution at all, and it isn't really required anyway, the relevent code was only in the camel provider since there was no other 'at startup' entry point.  And this might introduce problems with things not being registered before they are accessed.


--
Michael Zucchi <notzed ximian com>
"Evolution - Mostly Practiced By Dumb People"
Novell's Evolution and Free Software Developer


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]