configfacade.cpp File Reference

Go to the source code of this file.

Description

Draft for a facade to access and retrieve configuration values This was created as part of a first draft towards an application wide configuration system.

Later (around 2012) it became clear that we can not judge the requirements for such a system yet, so we deferred the topic altogether. Meanwhile, this facade is sporadically used to mark the necessity to retrieve some "parametrisation values".

A preliminary implementation is backed by a setup.ini file, located relative to the application binary.

Todo:

as of 2016, this seems not to be used much, if at all. The GTK-UI, which in itself is very preliminary, retrieves some values from configuration, most notably the name of the GTK stylesheet (lumiera.css is the default)

Definition in file configfacade.cpp.

#include "include/logging.h"
#include "include/lifecycle.h"
#include "include/config-facade.h"
#include "common/appstate.hpp"
#include "lib/searchpath.hpp"
#include "lib/util.hpp"
#include "common/config.h"

Macros
#define	KEY_CONFIG_PATH   "Lumiera.configpath"
	key to fetch the search path for extended configuration. More...
#define	KEY_PLUGIN_PATH   "Lumiera.modulepath"
	Similarly, this key is used to fetch the configured default plugin/module search path from the basic setup.ini This patch is used by the plugin-loader to discover lumiera plugins and extensions.

Functions
const char *	lumiera_get_plugin_path_default ()
void	pull_up_ConfigSystem ()
LifecycleHook	trigger__ (ON_BASIC_INIT, &pull_up_ConfigSystem)

Namespaces
	lumiera
	Lumiera public interface.

Macro Definition Documentation

KEY_CONFIG_PATH

#define KEY_CONFIG_PATH   "Lumiera.configpath"

key to fetch the search path for extended configuration.

Will corresponding value is defined in the basic setup.ini and will be fed to the (planned) full-blown config system after the basic application bootstrap was successful.

Definition at line 50 of file configfacade.cpp.