Re: [Evolution-hackers] Creating a new server type
- From: Dan Winship <danw novell com>
- To: Thomas Cataldo <thomas cataldo aliacom fr>
- Cc: evolution-hackers ML <evolution-hackers lists ximian com>
- Subject: Re: [Evolution-hackers] Creating a new server type
- Date: Wed, 06 Oct 2004 10:36:01 -0400
On Wed, 2004-10-06 at 15:10 +0200, Thomas Cataldo wrote:
> static CamelProvider obm_provider = {
> "obm",
> N_("Aliacom O.B.M."),
>
> N_("For contacts and multi-user calendering"),
>
> "obm",
>
> CAMEL_PROVIDER_IS_REMOTE | CAMEL_PROVIDER_IS_EXTERNAL |
> CAMEL_PROVIDER_SUPPORTS_SSL,
(IS_EXTERNAL is actually meaningless in 2.0. That should have
disappeared...)
In addition to what Not Zed said about implementing CamelStore, you also
need to set CAMEL_PROVIDER_IS_SOURCE here to make it show up in the
menu. Setting IS_SOURCE but not IS_STORAGE means that the provider is
like POP, meaning it won't show up in the folder tree, but evolution-
mail will call your CamelStore implementation to fetch new messages when
the user clicks Send/Receive, so you're going to have to fake that
properly too.
On Wed, 2004-10-06 at 21:44 +0800, Not Zed wrote:
> bindtextdomain (GETTEXT_PACKAGE, CONNECTOR_LOCALEDIR);
>
> You shoudln't re-bind-text-domain, as this will affect the rest of the
> application since this runs in the evolution memory space.
No, textdomain() is the one that libraries shouldn't call. (It sets the
default translation domain). bindtextdomain() just tells gettext where
a particular translation domain's .gmo files are. If you don't call it,
it will expect them to be installed in /usr/share/locale regardless of
where the rest of the package is.
-- Dan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]