[ale] Window Managers for X

Mon Sep 18 00:35:59 EDT 2006

And we see statisticians do that daily.  ;)

Here is some more (all of it that is pertinent to evas rendering
anything) of the quote from the previously quoted IRC conversation:

23:25 <@raster> everything is software rendered
23:25 <@raster> all pixels are caluclated with the cpu
23:25 <@raster> and pumped to the gfx card
23:25 <@raster> the default engine is software_x11
23:25 <@raster> (for evas)
23:26 <@raster> and e17 asks for that egnine by default
23:26 <@raster> the only other option is the xrender_x11 engine
23:26 <@raster> and that is only viable if it built with xrender support

> The library
> that handles all the eye candy in E17 is called Evas. Th following is
> full quote from the website:
> 
- -- cut website quote --
> 
> If you read what I wrote, I said it will run "best" on OpenGL
> hardware. I didn't say it wouldn't run well in "software mode." Nor
> did I ever say it will run dog slow. 

I apologize for skipping over the "best" part.  It felt as if you were
insinuating that it would not run well without it, and I have run it
just fine with no OpenGL and lacking CPU (i.e. - 300MHz G3 clamshell)
with no noticeable effects.

> But the pixmaps (images) have to
> be stored somewhere. And for all the pretty eye candy to be there,
> some sort of images will be used.
> E16 doesn't use as many as E17,
> therefore, E17 uses more memory. It is a simple conclusion.

Not all eye candy comes from images.  Much eye candy comes from
procedures that perform some sort of effect on an object that is already
drawn.  Note:  I cannot speak for the code of any WM, as I have not
assisted in their writing.

I apologize if my post came off as an attack.  E16 and E17 are great
WMs.  I hate to see others knock what is good when they are seemingly
spewing hot air (as happens all too often in the Open Source community).

- --

Richard Kolkovich

> 
> On 9/17/06, Richard Kolkovich <sarumont at sigil.org> wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On 09/15/06 12:38, James Sumners published:
>>> I didn't bring up memory usage for a reason ;)
>>>
>>> E is all about eye candy.
>> E is about having power, flexibility, and eye candy without being overly
>> "in your face" OR hogging resources.
>>
>>> I believe the most recent releases of E16
>>> have been fixing up some of the memory issues, but I don't recall
>>> since I don't use it anymore.
>> I cannot speak here, as I have not used E16 in probably 2 years.  I have
>> been running E17 from CVS.
>>
>>> E17 will be even more of a memory hog
>>> because of all the new pretty effects. It will also run best on OpenGL
>>> hardware.
>> Have you ever run E17?  I am guessing that you have not, as these
>> statements are 100% inaccurate.  On my G3 clamshell, I booted into X
>> running E17, ALSA and pbbuttonsd (power management) with less than 35MB
>> of RAM used (oh...running gkrellm2, as well, to display this handy
>> figure).  I had not turned down any of E17's "eye candy" features.  I
>> think this sufficiently dispels this false statement.
>>
>> OpenGL hardware?  Here is a recent log from #e on freenode:
>>
>> 23:25 <@raster> everything is software rendered
>> 23:25 <@raster> all pixels are caluclated with the cpu
>>
>> OpenGL hardware, when I last checked, does not assist the CPU in
>> calculations.  It is only used when the OS's OpenGL implementation is
>> called, thereby using the GPU, rather than the CPU, to render.
>>
>> I hope you will find this information enlightening (pun intended - har
>> har).  Ignorance is a dangerous thing.  Please avoid it in the future by
>> not speaking of things which you do not know.
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFDiIvfXtD1KVAIbARAh0pAJ9lK1oAibf0ah7U9ogPY9sEJolU/wCg8pdR
Io7/Bn3jf14r6LNw8xzyhO4=
=gjAx
-----END PGP SIGNATURE-----