everburning

So, our bug tracker is dead. It seems the server it was hosted on had a massive failure of some kind and the the guy that was hosting it for us wasn’t making backups.

If you were one of the few people that actually had something in there that wasn’t closed (of which, I think 80% of those were entered by me anyway) you’ll need to re-send us your bug again or we’ll forget.

You can either find us in #ewl on irc.freenode.net or send an email to the enlightenment-devel mailing list hosted on sourceforge.

We’re currently waiting for the new e.org server to arrive so we can get a new bug tracker setup. Sucks that we lost all the current bug data. There was a lot of good stuff in there.

Well I’ll be off on another work trip next week. I’m flying out at 1630 on Friday, should land in Amsterdam sometime Saturday morning.

I’ll be there until the following Saturday when I fly back at 0600, I think, landing in Toronto around 1200hrs.

Should be a fun trip. I’m flying out on the Friday and don’t have to start working until Tuesday so I’ve got three days to tour around the city (assuming I’m awake on Saturday). Then I’ve got the next Friday off as well. We were suppost to fly back on Friday but it’s a lot cheapter to stay until Saturday morning. Plus, I’ll have evenings to do as I want during the week (although I’m not exactly sure where we’ll be but it isn’t in Amsterdam).

All I’ve got to do is find somewhere to sleep for those three nights until I move to the hotel that work is booking for me. Minor details.

Oh, this is just cruel. Making a post on what sounds like a tasty, tasty lemon chicken then leaving the rest of the lemon loving world out in the dark as to what’s in it.

For the love of all that is lemony, let the drooling masses know, what’s in the chicken?

EWL has been using the ecore_config subsystem to handle all of its configuration tasks. I converted it over to ecore_config fairly soon after its appearance in CVS. The way EWL worked was to hook into what is called the _system portion of ecore_config so that its configuration wouldn’t show up if an application was also using ecore_config.

Now, while this seemed like a good idea at the time, the tool to edit the _system data for EWL, examine, has been busted for quite a while. Meaning, we can’t change any default values in EWL. We have some command line options but there limited.

So, I ripped it out. It doesn’t work, so we don’t use it. In its place we have a simple system to use plain text key/value pair files. There is a system configuration file in @PACKAGE_DATA_DIR@/ewl/config/ewl.cfg that contains all of the possible keys.

# Ewl default configuration file.

#/ewl/debug/enable = 0
#/ewl/debug/level = 0
#/ewl/debug/segv = 0
#/ewl/debug/backtrace = 0
#/ewl/debug/evas/render = 0
#/ewl/debug/gc/reap = 0
#/ewl/theme/print/keys = 0
#/ewl/theme/print/signals = 0

/ewl/cache/evas/font = 2097152
/ewl/cache/evas/image = 8388608

/ewl/engine/name = evas_software_x11

/ewl/theme/name = e17
/ewl/theme/icon/theme = Tango
/ewl/theme/icon/size = 22x22

#/ewl/theme/color/classes/override = 0
#/ewl/theme/color/classes/count = 0
#/ewl/theme/color/classes/0/name = class_name
#/ewl/theme/color/classes/0/r/1 = 255
#/ewl/theme/color/classes/0/g/1 = 128
#/ewl/theme/color/classes/0/b/1 = 255
#/ewl/theme/color/classes/0/r/2 = 255
#/ewl/theme/color/classes/0/g/2 = 128
#/ewl/theme/color/classes/0/b/2 = 255
#/ewl/theme/color/classes/0/r/3 = 255
#/ewl/theme/color/classes/0/g/3 = 128
#/ewl/theme/color/classes/0/b/3 = 255

Anything beginning with a # is a comment. So we’re really only using 6 keys out of that file.

Along with the system config each user can have their own overrides in ~/.ewl/config/ewl.cfg.

The content of these files can be configured with the ewl_config command, or edited by hand if desired. ewl_config can either be used from the command line using the -set and -get flags or in GUI mode. If you run ewl_config as root, or someone with permissions to write the system file, you’ll be able to set the system configuration.

The ewl_config code can also handle application configuration. By calling Ewl_Config *ewl_config_new(const char *app_name) you’ll be able to set and get configuration for your application. This will work with user, system and command line configuration. If you need to save the system configuration there is a int ewl_config_can_save_system(Ewl_Config *cfg) that returns TRUE if possible, FALSE otherwise.

Application configuration will be stored in @PACKAGE_DATA_DIR@/ewl/config/apps/app_name.cfg and ~/.ewl/config/apps/app_name.cfg for system and user respectively.

The final piece to be completed for the ewl_config code in EWL is to to hook it into ecore_dbus to send messages when the configuration is saved. Then other instances of the application, or other users of the EWL library, can be notified when configuration is changed. This will allow us to have EWL update its theme as soon as the configuration is changed, assuming the user used ewl_config to do the changing.

As usual, bug reports to xcomputerman.com/bugs. If you want to discuss, either the enlightenment-devel mailing list or #ewl on irc.freenode.net.