structs are something else and we are discussing them... Also - you do not need access to the list count, so why provide such a thing? OK, so it might be useful to know, but not in the way you mean - an addition is just added to the end, and a deletion "realigns" the contents. The actual count is not needed to store efficiently...
A On Tue, Dec 20, 2005 at 10:18:08AM +0800, Phuah Yee Keat wrote: > Morten Nilsen wrote: > >Phuah Yee Keat wrote: > > > >>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 > >>... > >> > > [snipped] > > >that implementation would need some code to muck about with the keys in > >the library.. I don't like it.. > > Is it possible to support structures like this in your implementation? > Previously the structure for the sessions are as such: > > /entrance/session/1/name "Fluxbox" > /entrance/session/1/exec "startfluxbox" > /entrance/session/1/icon "fluxbox.png" > /entrance/session/2/name "kde" > /entrance/session/2/exec "startkde" > ... > > The entrance_config.c will then loads the names, exec and icons are > store them inside a structure. If we were to do the array approach, does > that have to be changed to this? > > /entrance/session/name/1 "Fluxbox" > /entrance/session/exec/1 "startfluxbox" > /entrance/session/icon/1 "fluxbox.png" > /entrance/session/name/2 "kde" > /entrance/session/exec/2 "startkde" > ... > > Then this will be unable to make array of structures that contains > arrays, as the original structure would have > > /entrance/session/1/name "Fluxbox" > /entrance/session/1/exec/1/name "startfluxbox" > /entrance/session/1/exec/1/path "/usr/X11R6/bin" > /entrance/session/1/exec/2/name "fluxbox" > /entrance/session/1/exec/2/path "/usr/local/fluxbox/bin" > /entrance/session/1/icon "fluxbox.png" > /entrance/session/2/name "kde" > /entrance/session/2/exec "startkde" > ... > > :) I feels that the current mock up way of handling list very nicely > done. The only thing which I do not like is the code that is needed to > load the "count" variable, determines what is the next index that I need > to add, managing lost indexes while deleting entries etc... > > Cheers, > Phuah Yee Keat > > >as for /entrance/path/*/name .. that's not a unique path, and can't be > >used as a key.. > > My bad, I was thinking more along the lines of how xml/html works with > numbered list and un-numbered list, and un-numbered list _is_ about not > having a unique key. I have to look more into the implementation of > ecore_config. > > 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
