(KainX)
Alright, I've got the config stuff working as planned. Epplet_Init() has the
same parameters as it used to. If you use config files, make sure to call
Epplet_load_config() AFTER calling Epplet_Init() but BEFORE attempting to
access config data.
Also note the function name changes: Epplet_save_config(),
Epplet_query_config_data(), and Epplet_modify_config_data().
SVN revision: 951
for instance accounting, every epplet has its own directory in
~/.enlightenment/epplet_config/<epplet-name>, transparent config file
handling is provided. Users only need to query for settings and change
settings. Config settings are saved automatically on exit, which
means that users MUST call Epplet_cleanup() before exiting. Every
epplet instance has its own config file. Also added a mechanism for
defining default settings.
Updated all epplets accordingly.
Look at ConfigTestEpplet.c for the details. It shows what instance it
is running as and keeps a record on how many times that instance
has been run in the config files.
SVN revision: 949
but I haven't tested it enough yet.
The idea is to run
Epplet_load_config_file("~/.whaterver");
assuming that the config file looks e.g. this:
a_number 123
some_word hello
my_string hello world
and then query for the keys in the first column using
char * s;
s = Epplet_query_config_file("my_string");
if (s)
{
/* s is now "hello world". */
}
Hope that's a good idea.
Cheers,
-- Christian.
SVN revision: 838
Michael Jennings
Christian Kreibich
Carsten Haitzler