On Wed, Feb 25, 2009 at 1:47 PM, Cedric BAIL <cedric.b...@free.fr> wrote:
> On Tue, Feb 24, 2009 at 10:33 PM, Gustavo Sverzut Barbieri
> <barbi...@profusion.mobi> wrote:
>> On Wed, Jan 28, 2009 at 9:04 PM, Toma <tomha...@gmail.com> wrote:
>>> Thought Id ping the mailing list about this:
>>>
>>> http://trac.enlightenment.org/e/wiki/Release
>>>
>>> As the top of the page says, we need to finalize the list of things
>>> TODO. Mekius mentioned removing a couple of the EFM todos and Id
>>> welcome that. Im in the process of finishing off the icons, but think
>>> some of the dialogs could either get the chop, or get renamed. One of
>>> these is 'Interactions', as it has a pile of thumbscroll options.
>>>
>>> Shall we set a date for closing off the TODO feature list? Any
>>> additions after that date will be bugs related to the features.
>>>
>>> I propose February 14th. Its close, realistic, and might dull the
>>> loneliness of Valentines Day. :)
>>
>> So time has come and we're working on that release list. In the last
>> days I've being working on some show stopper stuff like file
>> management and I plan to get ride of most items by March.
>
> Did the same on the eina front :)
>
>> Some items in the list are very demanding, like finish converting
>> ecore data types to eina, but Cedric has some pending patches in
>> queue. If people can help with these "easy" items, then we can work on
>> more complex stuff and get E17 released soon, making everybody happy,
>> with ready to use packages in most distros :-)
>
> All my pending patch are now in. It should not introduce any
> regression. Now e_dbus, efreet and ecore should only return Eina_List.
>
> Still on the TODO, but this could be done one after another with very
> small commit :
> - remove ecore_dlist (replace by eina_list)
> - remove Ecore_List2 (could be replaced by eina_inlist)
> - review every little loop in the code around list and check, if it
> would not be better to use EINA_LIST_FREE or EINA_LIST_FOREACH (at the
> same time, look if we can avoid useless strdup).
> - remove last user of evas_hash and evas_list (they did appear between
> the start of the move and the actual commit)
> - remove evas_hash and evas_list from Evas.
> - remove the last standing ecore_list (some use in e modules and ewl mainly)
> - move to eina module infrastructure for evas, ecore and e.
> - move to eina rectangle in evas.
> - move to eina error for displaying error message.
> - remove ecore magic and use eina magic.

Should ecore_list stay in and only the doubly linked lists replaced by eina?
If ecore_lists will removed, too, it is not only used in e17, but also
by some ecore internals, i.e. ecore_path_group.

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to