> It was disabled because it had bit rotted, didn't compile, and was a > casualty of our removal of Cairo from Servo. In order to bring it > back, someone just needs to reimplement it without using Cairo. > > This interacts somewhat with the work I'm doing on GPU rendering, as > we'll either have to disable the GPU path with a PNG compositor, or > have the compositor still be GPU based but just write out the final > framebuffer to PNG. I'd suggest the former method until after the GPU > rendering code lands.
Thank you, Jack. 2013/5/7 Jack Moffitt <[email protected]>: > It was disabled because it had bit rotted, didn't compile, and was a > casualty of our removal of Cairo from Servo. In order to bring it > back, someone just needs to reimplement it without using Cairo. > > This interacts somewhat with the work I'm doing on GPU rendering, as > we'll either have to disable the GPU path with a PNG compositor, or > have the compositor still be GPU based but just write out the final > framebuffer to PNG. I'd suggest the former method until after the GPU > rendering code lands. > > jack. > > On Tue, May 7, 2013 at 1:48 AM, Tetsuharu OHZEKI > <[email protected]> wrote: >> Hello, >> >> I tried command line options of servo, `-o` option does not work at >> now. I found the commit which is seemed to disable working `-o` >> options: >> https://github.com/mozilla/servo/commit/21cd74826979f6c60c2f6b0d14db2205db99fe6b. >> However, I cannot find why we disable it. >> >> So I have some questions. Could you tell me about these things?: >> * Why did we disable the output png file? >> * What do we need to re-enable its feature? >> >> Regards. >> >> -- >> Tetsuharu OHZEKI >> [email protected] >> _______________________________________________ >> dev-servo mailing list >> [email protected] >> https://lists.mozilla.org/listinfo/dev-servo -- saneyuki_s [email protected] _______________________________________________ dev-servo mailing list [email protected] https://lists.mozilla.org/listinfo/dev-servo
