GTK+ and 21.2

Doug> After seeing the "Call for Testers" for 21.2/22.0, I thought Doug> I would jump on the bandwagon. Thanks! Doug> I'm primarily interested in the GTK+ port. Bill Perry promised a merge by February 1. (To be precise, he said it was feasible and hasn't retracted that statement.) <nag> Well, Bill? </nag> Doug> When I run ./configure, I don't see anything about enabling gtk+. Nope, not yet. Doug> Has the gtk+ port been merged in with 21.2 yet? Nope, not yet. Doug> Is it the default toolkit? No, and it won't be default in the release. Right now GTK is "cool" but is not supported by lots of code that uses it. I'm hoping for an avalanche of extension and customization, but that will take fairly hardened "out-of-the-box-config? Just Say No" hacker types at first. (This is open to discussion, but preliminary discussion showed the Review Board is pretty much unanimously against defaulting to --with-gtk=yes in the release.) It probably will not be default in the betas, either. (Again open to discussion, but there is almost no support for it on the Board, I should revise that part of the release plan.) Doug> How do I compile xemacs with GTK+ support? To get GTK support, use the --with-gtk=yes argument to configure with source code that supports GTK. At the moment, if you want to work with ancillary support like actually using the GTK widgets to make Custom look nicer and stuff like that, check out the xemacs module with `-r gtk-xemacs' cvs.xemacs.org. This currently gives you a 21.1 XEmacs with GTK support. If you want to help Bill with the port (he has a tree of code that builds but doesn't quite run as of last report, some weeks ago), mail him directly, I guess. -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."