These files were old and suitable for human editing, the ecore_config is supposed to be more optimal on space, speed and nice API, not on editing the files by hand!
anyhow - that is the old edb stuff, which we have never tried to be compliant with... A On Mon, Dec 19, 2005 at 06:54:12PM +0800, Phuah Yee Keat wrote: > Morten Nilsen wrote: > >Andrew Williams wrote: > > > >>perhaps looking at this on an ecore_config API level, rather than on a > >>ecore_config binary tool parameters level would help. > >>We need generic list handling in ecore_config and it is something I have > >>pondered over much and never come to a satisfactory solution... > > > >that is what I was on about too.. the append stuff is just a useful tool > >for strings.. > > > >What I'm currently thinking about, is adding in a new type > >ECORE_CONFIG_ARRAY with the data structure written to the eet like > >%c\0%c\0[...]\0 where the first %c is ECORE_CONFIG_ARRAY, the next the > >type of data contained (ECORE_CONFIG_STRING) and [...] the items of the > >array packed together.. strings would be null-terminated and others > >having a fixed width, not needing separators.. > > > >does that sound reasonable? > > I have not gone thru the source of ecore_config yet, but at first I was > thinking more of maintaining the current way of making a list, say > > /entrance/path/0/name > /entrance/path/1/name > ... > > for numbered list, as it already is previously for the hardcoded > sessions in entrance, the only difference is that the tools that update > this conf file have to do more work. Its up to the tool as well whether > we need/want "/entrance/path/count" or not. > > Not to highlight that once we have numbered list, we might want to have > un-numbered list as well, maybe > > /entrance/path/*/name > /entrance/path/*/name > > again, the implementation is solely on the tools/api/ecore_config, no > changes to the conf file standard. > > Just my initial thought. > > Cheers, > Phuah Yee Keat > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
