On Mon, 22 Feb 2010, Gustavo Sverzut Barbieri wrote: > people should use eet directly. ah ok, now i got it. I thought the whole configuration system will be abandoned, which made me quite confused since the whole desktop environment uses it.
Im not fully inside all e17 libraries, but if a centralising is preferred over single configfiles a wrapping of eet through ecore_config might be useful. I'm not quite sure if i would prefer a central configuration database over single per-application files, tough it obviously would have some advantages. But I'm still somewhat biased from the horrible windows registry. I think single configuration files are not so much exposed to data loss, as caused e.g. by a power loss. Perhaps the configuration data of one application is lost which had written the file in that moment, but not that of the whole system. Furthermore it's much easier to restore the default configurations with single files. E.g. the itask-ng module is quite unstable and every now and then i have to reset the configuration before starting e. But as i said some of my objections might be just prejudices, if it's well done a centralising might be a good idea. -- buergi ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
