On Wed, 24 Mar 2010, Carlos R. Mafra wrote: > > 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. > > I am sorry for not looking deeply right now, but is that MMX/assembly > stuff being used at all?
on certain things, it probably is. i've been eyeing that, but decided to leave it be for the moment. > I have a modern laptop and all that, and this is what I get in the > end of configure > > Use assembly routines for wrlib : no > Use inline MMX(tm) x86 assembly : no that's because "modern" today is x64, and that part only gets picked if you have x86. > > So at least in my case there is no tweak at all. Oh, and now I see > this in configure.ac: > > # until we fix it, leave it disabled > asm_support=no > mmx_support=no but i think you can still enable it by hand... comments not always reflect reality :) > For me the idea of getting rid of wrlib and using cairo > seems nice because I think having a graphics library exclusively > for wmaker has smaller chances of getting better/cleaner/faster > than using one which is actively developed. > > If we can pass the responsibility for the graphics stuff to > cairo instead of nurturing our own library (which probably > a _lot_ less people review or will be able to fix bugs), > I think it is worth. > > But I guess it will be a huge effort to get rid of wrlib. seconded. but it doesn't mean it should not be tried :) -- [-] mkdir /nonexistent -- To unsubscribe, send mail to [email protected].
