On Tue, Jul 29, 2014 at 08:53:05AM +0900, Carsten Haitzler wrote:
> > 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.
Ah now, if you're putting facts in front of my dreams, we're not going
to get anywhere :)
> 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
So I was thinking about a "minimal eye candy mode", like I believe e17
had early on when you set it up.
Isn't there a way to disable at least some of the work it does to make
things look good?
For instance, is it possible to run the main event loop less often?
Disable all things that move if not needed like the 'window is not
responding spinning stuff' which did improve my battery after I turned
it off?
I know you have no control over what the 3D drivers do, but you have
control over what you feed them :) as well as how often e wakes up.
> 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
That's fair obviously :) and you also know what's possible and what's
not as well as how much some of those are, but somehow I was hoping that
there would be low hanging fruits which yield degraded performance but
save battery.
1) Aren't there any other such items like the one you just gave me (turn off the
spinning circle?)
2) Can't e18 be made to sleep longer between event runs?
If I'm not getting it, and just wishful thinking, tell me and I'll go
away :)
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
------------------------------------------------------------------------------
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
