Re: [Opensync-devel] plugin paths and configs

[Chris F. <cd...@fo...>]

I've added a new API call:

	const char *osync_plugin_get_default_configdir();

This returns OPENSYNC_CONFIGDIR plus a G_DIR_SEPARATOR_S.

I've also updated google-calendar to make use of this, to remove the
need to specify a location for the .xslt files.

- Chris


On Thu, Jul 22, 2010 at 07:29:18PM -0400, Chris Frey wrote:
> Hi,
> 
> Is there a way to find the defaults directory (where the default config
> starter files are stored) automatically inside the plugin?
> 
> The google-calendar plugin has an advanced option in its config that
> holds the path to where its .xslt files are.  It would be nice to
> be able to make this an optional specification, so the plugin could
> find the default-installed .xslt files without the user needing
> to know the directory hierarchy of libopensync.
> 
> I notice that osync_member_get_config_or_default() uses OPENSYNC_CONFIGDIR,
> but there's no API call to return this directory name that I can see.
> 
> If this isn't possible with the current API, anybody have objections to
> adding one?
> 
> Thanks,
> - Chris
> 
> 
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Sprint
> What will you do first with EVO, the first 4G phone?
> Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> _______________________________________________
> Opensync-devel mailing list
> Ope...@li...
> https://lists.sourceforge.net/lists/listinfo/opensync-devel