On Thu, 24 Mar 2005 00:11:33 -0500 Dustin Fraze <[EMAIL PROTECTED]> babbled: > Hello, > While looking for a few simple fixes to get my feet wet with e17 > development, I found a few places with a "FIXME: xyz needs to come from > config". I've seen this in the main e code, as well as a few modules, > and I haven't bothered grepping the rest of the code yet. > > The issue I've run into is *where* exactly this config should be > placed? I think it should be a .db file, like the entrance config. > However, I think that because we are trying to build an "e17 desktop", I > beleive we should try to merge all the .db files into a single location. > One single enlightenment.db, preferably placed in /etc, or perhaps a > copy placed in the home directory of the user; allowing them to > manipulate it (or perhaps both? With a sort of over-riding capability, > so that admins can set skeleton config on the one in /etc, and the user > can customize based off of that template in their /home), that contains > the settings for most (all, in a perfect world?) packages built on the > enlightenment foundation libraries? > > Is anybody opposed to this? Or are there any other suggestions? If I > hear some support, I'd be more than happy to begin making the necessary > changes to *all* the programs currently in the CVS repository. Though > it'd be a pain to do; if it could get done before the end of the mini > freeze, then hopefully enough people would get the idea, and new > developers would also throw their configurations in said file. If not; > perhaps I'll just keep my mouth shut, and go back to finding something > else fairly easy to get me started with E. ok... 1 big db file for all efl apps? no way. BAD move. now as for where does e17 keep its config? e_config.[ch] take care of that. you can just add to the struct (and tot he descriptor setup) and ti will save/load and repopulate the struct autoamtically. the fiels are held in ~/.e/e/config/ in a collection of .cfg files that are rather small (most are gadman cfg files for gadman geometry per gadman managed module) the e.cfg is e17's core config - managed by e_config.[ch] :) the reason we did this is we have more complex stuff to save that ecore_config lets us do at the moment. e_config.[ch] is intended as a wrapper layer that does let us slide in new config back-ends behind ti later if we want. BTW - you need to subscribe to the list if you expect your mails to go to it :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 [EMAIL PROTECTED] Tokyo, Japan (東京 日本) ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel