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

Jake> What about if a different tarball is required for unix vs Jake> windows? SY> Why would that be necessary? Surely a source tarball is a SY> source tarball is a source tarball? Or does that piece of SY> crap that microsuck calls an OS have a different idea as to SY> what source is? No. Bob thoughtfully provided a Microsoft port in a separate subtree, that's all. And for Windows, it kinda makes sense for the "tarball" to maybe be a zipfile, or even a .exe self-extractor. SY> 2) Port xoobr to elisp and make it part of OO-Browser. (this SY> would be my preference) Jake> Sorry, this would be beyond my current skills and available Jake> time. SY> That's a shame, oh well, maybe someone down the track will SY> look at it and say "I bet I could do that in lisp..." :-) More power to 'em. But ... this is beyond _my_ current skills and available time. By which I mean to say both ECB and oo-browser provide perfectly reasonable text-based tree widgets; it only makes sense to include xoobr for its "sexy" graphics. That means a native widget, which AFAIK only Andy knows how to do. -- 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.