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
...
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.
that implementation would need some code to muck about with the keys in
the library.. I don't like it..
as for /entrance/path/*/name .. that's not a unique path, and can't be
used as a key..
I've just fine-thought my comment, and I'm about to write a bit of
testing code..
in the end, my idea will add an ecore_config_array_get() that returns an
array of type void ** with the last pointer being null.
Cheers,
--
Morten
:wq
-------------------------------------------------------
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
