| |||||||||||
|
| |||||||||||
Long-term death of bitmaps: Compositer policy?Long-term death of bitmaps: Compositer policy?Posted Jul 30, 2004 1:05 UTC (Fri) by AnswerGuy (subscriber, #1256)In reply to: Long-term death of bitmaps by pm101 Parent article: X at OLS Sounds like that would just be a byproduct of rendering to the virtual frame buffer and allowing a compositer policy to manage the scaling to the real display. JimD
(Log in to post comments)
Long-term death of bitmaps: Compositer policy? Posted Jul 30, 2004 8:03 UTC (Fri) by pm101 (guest, #3011) [Link] It really wouldn't -- the problem is double scaling. You lose quality. If you render a 24 pixel font, and scale it to 18 pixels, it looks worse than the original font rendered at 18 pixels. It looks even worse if you stretch it to 48. You could render at 400 pixels, and scale, but it would suck in terms of performance, memory, etc.It'd be nice if the input to the compositor could be vector, so that fonts and so on would come out nicely.
|
|||||||||||