[747] in java-interest
Re: Native Tk
daemon@ATHENA.MIT.EDU (Jayson Raymond)
Tue Jul 18 15:55:24 1995
To: Kacper Nowicki <Kacper.Nowicki@fuw.edu.pl>,
"java-interest@java.sun.com" <java-interest@java.Eng.Sun.COM>
Date: Tue, 18 Jul 95 10:41:20 -0500
From: Jayson Raymond <jraymond@connectsoft.com>
-- [ From: Jayson Raymond * EMC.Ver #b.2.5.06 ] --
I'd like to second Kacper's desire to see TK available in Java. I'm
beginning a project that I'd like to be able to port to a HotJava applet as
it becomes more widespread. If I can count on TK support being there, I can
begin right away in C++ with TCL/TK, and later port to Java/Tcl/Tk.
It would almost seem the TCL team could drop a number of their current
planned tasks and focus instead on a Java port, since those initial goals
would fall out as a result, including: Unicode support, platform
independence, and security. But of course, I am likely basking in the
blissful ignorance and simplistic world of a one sided view. Certainly the
efforts to strip Tk from it's X dependencies are right on the money.
And whatever the basis for Mr. Browns opinions, TCL/TK on Java would provide
a plethora of existing tools and support to Java. TCL/TK already exists on
the Mac and PC, so it would appear a large part of the new AWT would already
be done. It's seems so obvious to me that I must be missing something.
How much collaboration is occurring between these two teams? Java and
Tcl/Tk certainly compliment each other well. Together I can make the case,
in this primarily Windows company, to avoid the platform specific pitfall
of the Visual Basic / VBX route.
--Jayson
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
