Therein lies part of the problem.. evas should not
depend on ecore. If one wants to write some lib that
needs list/hash/file handling, then one is faced with:
a. link with evas and use its list/hash routines,
and something else for file handling, possibly ecore's..
b. link
Well there already exists lists and hashes in Ecore_Data and Ecore_File
should handle the file handling. There are slightly separate list data
structures in evas but that was done so evas dosen't depend on ecore.
dan
On Sat, 2005-06-11 at 08:10 -0400, Jose O Gonzalez wrote:
> I have a 'wis
I have a 'wish' for things I'd like to see in e..
not in e the wm, there are enough wishes for things in
there already :), but in e as in the efl's.
Two specific things to be exact:
1. A general purpose "list/hash" lib.
2. A general purpose "file" lib.
