(KainX)
Major restructuring and cleanup. I think the new standard should be pretty
self-explanatory, but let me know if you have any questions. CVS developers,
PLEASE read epplets/Makefile.am carefully to see how it all works now.
Icons are stored in epplets/icons/ and are installed into
$EROOT/epplet_icons/. All miscellaneous data files (including images) are
stored in epplets/<epplet name>-data/ and are installed into
$EROOT/epplet_data/<epplet name>/. Also note that, if you're going to use the
same old aircut3.ttf and bg.png in your help section, add your epplet's name
to NEED_BG and NEED_FONT in epplets/Makefile.am. Do NOT commit duplicates of
those two files.
SVN revision: 1394
(gilbertt)
Changed the Makefile.am to put epplet images in $EROOT/epplet_data.
I wanted to have epplet subdirs under this directory, but it really
complicated the Makefile, so I left it for now. It was easy for me the make
the changes with sed this way too ;)
Any stuff your app needs to install should go in epplet_data, preferably
with the filename prefixed with the name of your epplet.
Flame me if this bugs you...
SVN revision: 1345
(gilbertt)
Changes to E-Clock.c E-Areas.c Emix.x E-Sys.c E-Mountbox.c E-Load.c
E-Memwatch.c
Using atexit(Epplet_cleanup) prevents all those "mulitple spawning on
startup problems" people get.
SVN revision: 1269
(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
Tom Gilbert
Carsten Haitzler
Michael Jennings
Christian Kreibich