On Mon, 28 Jul 2014 15:59:11 -0700 Marc MERLIN <[email protected]> said:
> On Sat, Jul 26, 2014 at 11:55:27PM +0900, Carsten Haitzler wrote: > > e17 just thrw a few dumb large textures (big triangle pairs to make rects). > > e18 > > + throws much more geometry at gl. all the text in e (titlebars, menus, > > shelf) is renderd as text. it uses less memory and is actually far more > > flexible and powerful, and it works fine if you aren't re-rendering the > > bits you don't need to. > > > > i have an intel laptop, intel desktop, nvidia desktop, only accel-less > > laptop, another intel laptop, another nvidia laptop (nouveau)... i know of > > other drivers. i have far more than just one machine. > > > > if you don't have extensions to partial-render, then it full renders. full > > rendering is far more in e19 vs e17. that's not going to change any time > > soon. more complex gadgets will cost more. text with soft drop shadows or > > glows will cost a lot more. they don't get held in memory as a > > texture/pixmap - they get generated on the fly. > > I understand that, but would it make sense to have an e config option > for "less bling, more battery" that one could switch to by sending a > command from e from ACPI? i'm sorry - but no. it's like asking bmw "could i have a small button in my car that converts my x6 suv into an i3 electric car? it'd be so much better to roll around town!". it's not so simple. > Basically I'd want e18/e19 to become as basic CPU-wise as twm if I'm on > batteries and not moving windows around. e has no choice in this matter. it's a deep complex bi-product of many many many factors - partly canvas itself, its content, design choices and much more. a lot of it is a direct result of input from apps (more text in titlebars == more triangles to render (1 per char), and apps decide the text that will be there - they also decide how many windows you have and min/max size etc.), input from a user (choosing where their windows are, how to lay them out, what gadgets and icons they want in their shelf etc. etc.), and some styling... and much more. in addition drivers create a big part of the problem. some (all the egl/gles2 drivers in tizen support this extension and even more - also support partial swap which affects gl clients). i don't know if the intel egl/gles2 drivers support buffer_age in x11 - they may so try that. you can try force triple buffer mode in in advanced settings in compositor settings but beware this may screw up if your driver decided to quad buffer all of a sudden, or stop working in a sequence which seems common enough on. nvidia support buffer age which allows redraw minimization in glx. this affects things a lot. also there simply also is internal driver cost - how much work does your driver do in terms of copying, spinning to sleep etc.. all of this is unable to be controlled. some drivers work great, some so-so, some badly. why don't you poke the intel driver devs to support buffer-age in glx/ that'd get you most of your mileage and they (intel) were the ones who initiated the buffer_age extension in khronos. https://www.opengl.org/registry/specs/EXT/glx_buffer_age.txt and yet (first 2 guys are definitely intel - or last i knew) THEY don't support it, but nvidia do? > Would that be possible? :) no. as above. it's not so simple. and it certainly is not something to put into e. if anything you are asking for evas to do things like cache rendering of objects (individual ones and entire object trees) into textures to avoid more geometry. this is not simple - it is in fact a pain in the butt given current evas internals. you can do this EXPLICITLY via 2 mechanisms in evas - map and proxy. these both have bugs in dark corners that do things like affect the connman. epluse and pkgkit popups where the clipping of content goes wrong as a result. this is basically impossible to fix because fixing this will almost 100% certainly just create a new bug to hunt. the solution is a rewrite of the render core to simplify it and put these concepts into there "in stone". but i never have the time to do this, partly due to emails like this, patch reviews, other bug reports and a continual stream of other mentoring, and even more i can't mention. so until then - you have what you have > Thanks, > Marc > -- > "A mouse is a device used to point at the xterm you want to type in" - A.S.R. > Microsoft is to operating systems .... > .... what McDonalds is to gourmet > cooking Home page: http://marc.merlins.org/ | PGP > 1024R/763BE901 > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ Infragistics Professional Build stunning WinForms apps today! Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future. http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
