jason r tibbetts firstname.lastname@example.org wrote in message news:email@example.com…
Quoting Phil Tomson firstname.lastname@example.org:
OK, I’ve finally joined the world of MacOS X. (It’s good to be here:)
I want to quickly port some existing Ruby/Tk apps. I noticed that there
is an Aqua Version of Tk on the Apple downloads site. Would that work, or
should I just get the X-Windows version.
Wow, I didn’t know about the Aqua version, but I unless it turns out to be
bug-ridden, I would unquestionably use that one instaed of the X-Windows
version. X-Windows on OS X works well, but they look, well, X-Windows-ish.
If the Aqua version is anything like the Java version of Cocoa, you’d be
hard-pressed to tell the difference between a native OS X app and a TCL-
Yeah, I’d much rather use the Aqua version, but I’m wondering if it’ll
work with ruby? Is it just a simple matter of setting the TCL_LIBRARY
env var? Probably not, since we actually need RUBY_TK_DLL built for
Ruby. So I suspect that we can’t use the ‘out-of-the-box’ Ruby
(1.6.8) that comes with OSX. Probably have to compile from source and
somehow provide the path to the Aqual Tk libs.
What are the underlying mechanics here? Does configure look for Tk
libs and then build the Makefile based upon whether or not it finds
BTW, where’s the link to the Aqua version?
If you get it working, please let me know.
…Of course, I’d rather use RubyCocoa than Tk, but this is for some
already-existing apps that I don’t want to take the time to change.