On Sun, 24 Feb 2008 18:43:49 +0000 Ethan Grammatikidis <[EMAIL PROTECTED]> babbled:
> On Mon, 25 Feb 2008 03:08:27 +1100 > Carsten Haitzler (The Rasterman) <[EMAIL PROTECTED]> wrote: > > > On Sun, 24 Feb 2008 09:13:03 -0500 jack wallen <[EMAIL PROTECTED]> > > babbled: > > > > e17 doesn't support pseudo-transparency - it is a nasty ugly hack and e17 > > won't be adding such awful workarounds into it. use a composite manager and > > a proper ARGB32 terminal mode with alpha or don't use e17 :) > > > > > I use aterm for all of my console needs. In E16 aterm can do > > > transparency just fine. However in E17 it can not. Is there a reason for > > > this? Is there a way to change that behavior? > > > > > > Thanks all. > > Hmm, this reminds me of a question I've been meaning to ask. E17 doesn't > flag it's background window as the virtual root; is there a reason for > this? I was thinking about xroach and xpenguins and the xscreensaver > modules and all the other fun little things which can run in the root > window. XPenguins has of course been ported, but it seems to me to be > somewhat wasteful to require them all to be remade as modules in order to > work with E17, and of course a non-coder or a busy coder who fancied some > obscure old root-window hack would be stuck without it. (I know I usually > think of such hacks when I'm swamped with stuff, I guess I'm looking for > light relief.) Then too there are file managers with desktop icon > facilities, and other useful things - efm may be progressing well but > tying ones choice of file manager to ones choice of window manager > doesn't seem quite right to me. actually it is absolutely right. if u have multiple apps drawing to the same window you end up with chaos. drawing REPLACES the original pixels- it doesn't layer, stack or handle them right. one apps draws then another can draw over whatever was there before - and has no idea what was done. there is no co-ordination of any kind. just for starters the dropshadow module draws shadows within the canvas - it's organised and co-ordinated so it works. animated wallpapers will render themselves. other applications have no idea whats going on as they are not part of the canvas. you soon enough end up with bad conflicts and rendering artifacts and problems. so that's why e will not expose its root window to anything. it will be chaos. if you don't believe me - you just need to study up more about graphics, rendering algorithms, techniques and X11. > -- > Ethan Grammatikidis <[EMAIL PROTECTED]> > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
