On Wed, Dec 5, 2012 at 9:42 AM, Carsten Haitzler <[email protected]> wrote:
> On Wed, 5 Dec 2012 07:58:10 -0200 Gustavo Sverzut Barbieri
> <[email protected]> said:
>
>> Hi all,
>>
>> Lately having to read more code than I'd like, but some stuff came to my mind
>> as cleanup. Please comment before I execute them tomorrow:
>>
>> - remove directfb
>
> ok

removed


>> - remove ifdef related to async pipe and image preload. Always enabled
>
> ok

you did that already before moving to single tree, my bad.


>> - remove cserve1
>
> ok

you did that already before moving to single tree, my bad.


>> - remove Evas pipe (up to discussion, but I rather remove it and the huge
>> amount of code that exist to support it). With the new thread system it
>> wouldn't work as is, we'd need to modify it anyway and I don't think it will
>> bring much gain.
>
> no.

ok, kept


>> - remove code to clip to an image/mask. Seems to not be working, it's quite
>> complex and nobody seems to be getting it anytime soon. It's better to come
>> to it again in a clean approach than try to fix what's in there now
>
> ok.

removed


>> - remove code, mostly commented, to handle filters. Nash started but it never
>> worked and there are mountains of code related to that commented or #if 0
>
> ok.

removed


>> - various general cleanups of commented or #if 0/1 in the engines.
>> Particularly in x11. Raster, could you check those? Likely you added most of
>> them.
>
> leave for now - shouldnt hurt. long queue of stuff to do.

ok, would be nice to review before release of single tree.


>> On a related note I wonder about xlib x xcb. I tried xcb in the beginning
>> "because it was cool" but our engines did not work properly and I reverted to
>> xlib since then (2007? 2008?). How is it now? Do we really have to maintain
>> xlib if xcb is working? Seems xlib is implemented on top of xcb now. Reducing
>> one engine in Evas and one in Ecore would be helpful.
>
> it's much better - very close... but xcb is misssign a few features - mostly
> ecore_x - xkb i think is one. xcursor another.
>
> maybe we need to make a hybrid xcb/xlib ecore-x - ie advertise async api's and
> emulate via xlib, with xcb really being async. not sure tho - longer term.
> keepit all now.

this one is trickier and will be left to some other day.


--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: [email protected]
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202

------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to