Re: ha ha, only serious

ms> As far as I understand the redisplay engine, it works at a far ms> lower level of abstraction than KHTML, so I don't think that'd ms> be a viable fit: all the layout and stuff is pretty much ms> backend-independent; the rediplay backends just ship out the ms> bits to the display. Maybe not, but that's what Bill is proposing. (For the second time; he suggested something similar with Gecko way back when.) He's suggesting that redisplay would create something like a DOM, and KHTML, or part of it would translate from that intermediate language to wire protocol. Note that a lot of the ugliness of redisplay comes from the fact that we can (and do!) set "widget is dirty" flags from Lisp, as well as all levels of C. That is just evil. ms> Yeah, but judging from the total size of the code, I'm ms> assuming it's reasonable. Sure. But that also assumes that that our other backends will be as good a fit for a Qt-shaped socket in the side of KHTML as Cocoa is! -- Institute of Policy and Planning Sciences http://turnbull.sk.tsukuba.ac.jp University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Ask not how you can "do" free software business; ask what your business can "do for" free software.