Re: xoobr: whoa there baby! Not so fast!

SY> OK, now I'm confused. That is /exactly/ what I meant. To SY> clarify, what should be done is either: I agree with your assessment of what should be done. Go ahead and do it. ;-) If you don't do it soon, and Jake has better things to do, then second-best is to live with the addition to core. Please note, Jake Colman has contributed as much documentation in the last 6 months as the rest of the community put together, and that includes your mega patch to the PUI docs. Isn't that more important than a few KLOC added to core? And both your solutions suck at least as much as putting it in core does: SY> 1) Distribute xoobr as fully self-contained source SY> tarball within the OO-Browser package. (*NOT IN CORE*) Better just distribute a README.xoobr containing the single line: Get sources here: http://www.xemacs.org/Downloads/xoobr.html. That way they'll always get the most recent version of xoobr, even if they don't actually build it for a year. But mostly, they won't get it at all, while we can trivially provide it to the majority (ie, non-Windows) of 21.4 users if Vin says OK. It's just a few source files and an additional few lines in the lib-src/Makefile.in.in, and then change one variable definition to add xoobr, plus a small amount of fairly orthogonal configure.in hacking. SY> 2) Port xoobr to elisp and make it part of SY> OO-Browser. (this would be my preference) Uh, do you know what you just said? Most likely, the right way to do this is to make the guts of xoobr a native widget (although I think lwlib-Athena already provides a tree widget, I suspect it's not as nice as xoobr's), and then it's not just distributed as part of core, it will have significant impact on the maintenance of other parts of core. All of the proposed solutions have strong demerits. But realistically, xoobr is a standalone application. That means we really should break it out, I agree. But by that very token, if we put it in core now, it will be simple to break it out later when real support for that becomes available. -- 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.