-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Cedric BAIL wrote: > On Wed, Jan 21, 2009 at 11:14 AM, Pierre Cassimans <cazz...@gmail.com> wrote: >> if i look to the roadmap in trac, i see a lot of "Finish Eina integration". >> Is there somewhere defined what exactly this means? > > Nop, sorry not enougth time to write it. > >> Is there somewhere a table with what functions have to be replaced (or a >> table with ecore_function=>eina_function) ? > > Not really as they not work always the same, you can't just replace > ecore_hash, or evas_hash directly by eina_hash. Same goes for > ecore_list and eina_list. > > Right now I have a serie of big patch that move from ecore_list to > eina_list most main library (not PROTO and others in sub dir). > > Regarding the removal of evas_hash, some code was added in e using it. > It need to be replaced. I will do it, but edje_editor, elitaire, some > in E-MODULES-EXTRA, enhance, enity, evolve, exhibit, engage, enna, > etk_server, exalt, extrackt still use it and are not on my TODO list. > It would still be good to remove evas_hash from them, so that I can > remove completely the macro that define evas_hash on top of eina from > evas. > > Regarding ecore_hash, I have a pending patch that remove it from > e_dbus. But not for elitaire, enhance, ephoto, epsilon, estickies, > ewl, exml, eke, ewler, etk_server and eyesight. As previously, this > list of library are not on my TODO list, but removing this user of > ecore_hash, will give us the opportunity to remove all ecore_hash > support from ecore. > > Now for each library needed for the release, and from my head, so > perhaps more to do : > > - eet: Just use eina_hash in eet_lib.c for the cache subsystem. (No > pending patch) > - evas: Remove evas_array_hash.c and use eina_hash for caching font > kerning in evas_font_*.c. (No pending patch) > - ecore: Remove all use of ecore_list/dlist. (Pending patch) > - edje: From my point of view, migration is done. > - efreet: Remove all use of ecore_list/dlist. (Pending patch) > - e_dbus: Remove all use of ecore_hash/list/dlist. (Pending patch) > - e: Remove last added evas_hash and evas_list (few lines, no pending > patch). Remove ecore_list/dlist (pending patch). > > That's all I have in my mind for the moment. I am working on dumping > as much as possible of this pending patch in the comming week, so it > should not be that long before more library are ready. >
Thx for the answer. So, is there a list of which dev has what on his TODO list? Also, do we have to wait till all the projects are up to date to remove the functions? Are all the project that you are summing up still maintained or are there projects that are dead or need a maintainer? How can we know that and can't we put a sort of grace period to the projects (and their devs) before we can take out the functions out of the EFL's? Cazze -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkl3A5gACgkQxOkkXk4ksMAOKACeL6olApRojAtzjKq0iag3toRp KMgAn13V9JD91bhmvKximvQyUJw/TWAS =O/T4 -----END PGP SIGNATURE----- ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
