On Tue, 11 Sep 2007 00:02:25 +0200 Michel BRIAND <[EMAIL PROTECTED]> babbled:
> Hi Raster, > > Very smart you are :) > Was there so many crazy people like me ? > As I were very busy (buried under a thousand of dully mails at work) I > went home very tired theses days... But I used a few moment to think of > your edc scheme and now it seems to me more powerfull that text files ;) > > Anyway I'll test your new implementation. well edc is a compact way of generating an eet binary blob from a text file. eet's data encoding *IS* data structures in memory converted to a neutral portable disk format. eet is all about being programmer friendly. it's about being able to take data in memory - dump to disk, and then be able to load it again into data whenever you want, and do it VERY quickly and use very little disk space. then idea is that this makes it EASY for a developer to write tools to make configuration etc. easy. they don't ever need to worry about parsing anything ever again - and they know that users can't really "break" it badly. this allows them to more easily break it with no safety net put in by the developer. but it might be a good debugging tool... :) > Thank and bravo! > Michel > > > Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> - Sun, 9 > Sep 2007 00:15:36 +0900 > > >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. > > > > ------------------------------------------------------------------------- > 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-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- ------------- 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-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
