I'm thinking about replacing the [source:/trunk/Coherence/docs/coherence.conf.example current config file format], which is based on [http://www.voidspace.org.uk/python/configobj.html ConfigObj], by an xml file. Reasons: * I'm unhappy with the format for the plugins, too many `[[[`s, especially as we have to support more than one icon * the config file will be created via the html interface anyway in some future * we need to instantiate plugins with the same backend, e.g. two backends using the FSStore. That's not possible with the old configuration. * another dependency removed Things I'm uncertain about: * how to de-/activate subsystem logging and level override * plugin de-/activation, in the old config file one could just comment something in or out, now I need that active attribute, or remove it completely or wrap it into an xml comment * same with the global nodes like `` PS: This should have little to none impact to places where Coherence is called as a module and the configuration is passed as a dict. {{{ #!xml 30020 eth0 yes no no Coherence Test Content FSStore tests/content image/png 120 106 24 .face GStreamer Audio Player GStreamerPlayer Elisa ElisaPlayer localhost iRadio IRadioStore Flickr Images FlickrStore 60 yes image/png 98 26 24 flickr-icon.png Coherence MediaStore MediaStore /data/audio/music /data/audio/covers /tmp/media.db image/png 120 106 24 coherence-icon.png Elisa is watching you AxisCamStore Cam 1 http://192.168.1.222:554/mpeg4/1/media.amp rtsp-rtp-udp:*:video/MP4V-ES:* Cam 2 http://192.168.1.222:554/mpeg4/2/media.amp rtsp-rtp-udp:*:video/MP4V-ES:* Buzztard Media BuzztardStore localhost 7654 Buzztard Player BuzztardPlayer localhost 7654 coherence.log }}}