On Wed, 24 Mar 2010, Johann Haarhoff wrote: > > could someone give me a quick rundown as to why it is beneficial? i'm > > not looking to hear "because it renders fractal gradients 5.128% > > faster", but why _really_ :) > > For me the main advantage is the built-in support for XRender (and by > extension hardware acceleration). So instead of having to tweak MMX/assembly > in wrlib you get the performance for free in hardware. > > The other option is to change wrlib to use XRender. > > There may be other advantages as well, but I think the combination of > Xrender/Xcomposite/Xdamage is becoming a requirement for a modern window > manager. More and more apps are starting to expect proper transparency > support via XComposite, and if you are doing XComposite, you might as well > use a drawing library that supports the fancy stuff in hardware.
so basically it can be considered as natural evolution, right? don't get me wrong, i'm not against it, i just want to understand. > That being said, it might be more effort than it is worth, so please make the > case for sticking with wrlib as well. (older) commercial unixes. my take is that for the free oses, there's no point in carrying every baggage (workarounds for rh5 and stuff that i just came across), but some effort should be made to keep wm usable on things like solaris, aix, and whoever else is still alive. cairo might not be an option here, so to a certain extent, wrlib is still needed. best would also be of course if they could be made to coexist (a compile-time option perhaps), but from this point, it's enough if wmaker1 (even without significant new features and stuff) is just kept working for some time to come, while wmaker2 (hypothetic scenario) gets cairo and the candy. -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
