On 10/12/07, Dr. Michael 'Mickey' Lauer <[EMAIL PROTECTED]> wrote: > > src/engines/ecore_evas_software_x11/Makefile > > src/engines/ecore_evas_software_x11_16/Makefile > > src/engines/ecore_evas_gl_x11/Makefile > > +src/engines/ecore_evas_software_sdl/Makefile > > src/engines/ecore_fb/Makefile > > Could you briefly summarize why we have to have different etk engines? > I can think about the framebuffer, X, and SDL having different means to > deal with "top-level windows" and such, however, why does the > difference of e.g. software_x11 and software_x11_16 need dedicated > engines for ETK?
Mostly due ecore_evas having different constructors and basic methods (get x window id, etc). If we had a BaseX11 (as I call in python-efl) we could just have one engine for that, covering xrender, x11, gl_x11, x11-16 -- Gustavo Sverzut Barbieri -------------------------------------- Jabber: [EMAIL PROTECTED] MSN: [EMAIL PROTECTED] ICQ#: 17249123 Skype: gsbarbieri Mobile: +55 (81) 9927 0010 ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
