>>>> "Jamie" == Jamie Zawinski
<jwz(a)jwz.org> writes:
Jamie> Hey, have you guys considered ripping out XEmacs's
Jamie> redisplay and just using KHTML?
On second thought, following up on your own "notably, neither [this]
nor [that] are on this list" logic, what problems does this solve?
I can see that it would surely fix the show-stopping "infinite X
protocol from an unchanged window" bug, and you're welcome to
emphasize that with a "Yes, dammit!" But I can't help feeling there
are more straightforward ways to address that bug, that might even get
into an XEmacs you can use this year. (I will personally keep this
approach in mind, though.)
So, what _else_?
On the other side.... I have to wonder how we go about linking
markers, text properties, and extents to things KHTML knows about?
Note that according to DESIGN.html the internal DOM object is not
available to KHTML at all, only implicitly via the Javascript
bindings. (Sorry, Bill.) We'd be committed to maintaining an
interface to the---deliberately unexported, op. cit.---internals, at
least, and maybe our own version of KHTML. I suspect this is going to
be true of most advanced redisplays; the work there seems to be on
browsers and word processors, not on powerful-editor-as-IDE. Would
anybody want to program in any of the fancy word processors now
available (let alone the Mozilla text widget)? Today's XEmacs
redisplay is undoubtedly an overcomplexified monstrosity, but I can't
help feeling that some of the complexity is a reflection of complex
problems being solved.
KHTML itself also surely depends on the Qt libraries. That means we
cannot link on Windows at least (unless the licensing for Qt has
changed since we last discussed a Qt port). Is Qt GPL-compatible on
Apple platforms? Anyway, so much for portability benefits (not to
mention the sure opposition of at least two of our most active coders).
--
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.