Re: [Evolution-hackers] Exchange Connector documentation/overview ?

[Not Zed <notzed ximian com>]

"you probably don't want to do that".

Things have changed in 2.2, and there are more extension possibilities.  For mail you still need to implement a CamelStore/Provider/Transport/etc, but the configuration/account stuff is a bit of a hack in connector.

So given connector is such a mess (i can say that since i never worked on it, and i'm prone to saying things like that about stuff i didn't work on - *shrug*), you might not want to use it as the starting point.

I don't know, for mail i guess could start looking at implementing a CamelStore.  Some of thats a bit of a mess too (i can say that since i did work on it and i know it is), but not an impossible mess - and there are more examples of it in the source tree at least.


On Mon, 2004-10-25 at 12:31 +0200, Jules Colding wrote:
> Hi all,
>
> I am trying to make a new plugin for Evolution using the Exchange
> connector as skeleton code. The plugin will give access to Exchange
> using Brutus instead of WebDAV, so I gather that the original connector
> is a good starting point.
>
> I have looked at the connector code and have come to the conclusion that
> my options are:
>
> 1) Stare at the code until I understand all the design principles (this
> could take days or weeks)
>
> or:
>
> 2) Ask the list if someone could point me in the right direction with a
> few good hints in the line of "You need to provide an implementation of
> the Foo and the Bar interfaces.."
>
>
> Thanks a lot in advance,
>   jules
>
> _______________________________________________
> evolution-hackers maillist  -  evolution-hackers lists ximian com
> http://lists.ximian.com/mailman/listinfo/evolution-hackers

--

Michael Zucchi <notzed ximian com> "born to die, live to work, it's all downhill from here" Novell's Evolution and Free Software Developer