>> And it'd be nice if Aqua was a >> client-server windowing system (I know, there's XonX - but at this >> time, >> I don't want *two* memory-hungry window systems on this powerbook). > > > This is very very true :) I agree. IMHO, the key to getting quality applications ported to OSX is to provide an easy migration path from Unix. I would like to use the Unix tools I know on OSX. That means a solid foundation of:Java 2, Python, Perl, X Windows, Tcl/Tk, Tkinter, glib, gtk+, even qt. Perl 5.6 is standard--although without tcl/tk--a serious omission that breaks many sophisticated Perl programs. I have heard glib, gtk, and qt can be compiled if one know the proper command line incantations, and I have successfully compiled tcl 8.3.3 and Python 2.1. But I had to use the trial version of Tenon's X to provide the xlibs. So for so good but I haven't tested Tkinter very thoroughly yet. An alternative that entails learning yet another new syntax and language is Jython. Jython runs in the Java VM so runs "out of the box" using Java Swing for a GUI on OSX. But then that doesn't help us run Perl Tk at all and means we miss the vast body of Perl modules out here unless we want text only interfaces. Tenon's X server is fairly expensive when you consider it doesn't support all x-based applications--there are menu problems and of course it is a big process to run. I submitted feedback to Apple on OSX Beta that I considered a robust X Server that runs as a window under OSX (like Tenon's and not like Darwin XonX) key to attracting a lot of existing Unix software quickly to the platform. I am not sure why they decided not to provide a solid X Server--I think it is a mistake, but I guess they have their reasons. I wish they'd tell us why. --BTW, Justin, climbed a 5.9 today so I did get away from the computer for a while and feel much better, thanks for the advice ;-)
