ok- for all the crazies out there who insist on text config files i added: 1. a little extra info to eet data blobs to also encode data type. 2. eet api to parse and dump text config files to and from eet config data blobs 3. a small eet util to extract, insert, encode and decode such blobs.
you will need to wrap this up yourself in shell scripts as you see fit - the config format is very edc like (for edje files) and the parser is not forgiving - make a mistake and it won't be happy and not tell you much. you can extract e's config for example: eet -d ~/.e/e/config/default/e.cfg config out.txt vi out.txt eet -e ~/.e/e/config/default/e.cfg config out.txt 1 any eet file can have elements extracted - if they are eet config blobs it can decode. other blobs may be images or other data - the tool doesn't handle that. beware - config files will be LONG. my e.cfg is a 20kb binary blob - but as text expands to over 10,000 lines of config. parsing of these is slow compared to the binary blobs which is lightning fast. you have all u need to screw with files as you like - be warned that if you do so you are on your own. i implemented this just to keep the "i must have this as text" complainers happy. it doesn't buy you anything but a way of screwing your config up. i issue this warning now. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
