On Fri, 27 Aug 2004 20:30:02 +0000 Shish <[EMAIL PROTECTED]> babbled: > >>> Log Message: > >>> added ecore_evas_gl_x11_window_get() > >> > >> Is this not redundant? It doesn't do anything different from > >> software_x11_window_get() as far as I can see. Feels like unneeded bloat. > > > > Yes, but the function name clearly indicates that its specific to the > > engine that's used so it makes sense to have an extra function for the > > GLX11 engine. > > Which reminds me of something - why is it the app's job to decide which > display engine to use? I would have thought it better to have a generic > window_get() function for the apps to call, and based on the user > config, it either returns a software_x11 or a gl_x11 window (or > framebuffer, etc). That way the engine can be set globally or in the > per-app config.db, but the user always has the choice of whether to use > software or hardware rendering based on their hardware at the time, different engines have different properties. gl CANNOT do shaped windows, nor can it render to pixmaps to avoid damage redraws. also gl drivers and libs are flakier. gl also suffers display quality degradation as well as more overhead than software for small canvases. i leave it up to the app to decide on the engine itself. -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 熊耳 - 車君 (数田) [EMAIL PROTECTED] Tokyo, Japan (東京 日本) ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=5047&alloc_id=10808&op=click _______________________________________________ enlightenment-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
