On Tue, Nov 1, 2016 at 10:14 AM, Stefan Schmidt <ste...@osg.samsung.com> wrote: > Hello. > > On 28/10/16 04:28, Carsten Haitzler (The Rasterman) wrote: >> >> 3. xcb was a valiant effort, but it is not even 1:1 feature for feature up to >> date with xlib. it's off by default because of this and we need xlib for gl >> anyway. we cant dump xlib. it's just a lot of code in our tree that we likely >> could remove to clear out some "cruft". not to say work on xcb has been bad. >> it's been good. it's a very very large amount of useful code but it just has >> never proven to be any real big gains and lack of full featured >> implementation >> (it's 98% there) means it kind of isn't useful. so how about we drop it to >> simplify? > > It would reduce code size, code complexity, maintenance, build > configurations, etc. Removing it gets a thumbs up from me. :) > > I was thinking about it before but did not ant to stomp on Devilhorns > feet as he was still actively maintaining it. It is also a bit unclear > to me if there are real world users out there. I would have hoped they > would have replied by now. Maybe give them another week before the removal.
is the removal concerning also ecore_x ? Vincent ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
