> Removing wrlib will be very disrupting to wmaker stability, but
> the end goal seems worth pursuing. And we'll keep the stable
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.
That being said, it might be more effort than it is worth, so please
make the case for sticking with wrlib as well.
also, how stable is the cairo api? i'd think it is, it has been around
long enough, but i just have to ask ;)
I don't know.
-----------------------------------------------------
This message was sent using Obsidian SWiTCH web-mail.
Obsidian SWiTCH - an Obsidian Systems company.
(0860) 055-911 - http://www.switch-it.co.za/
--
To unsubscribe, send mail to [email protected].
