1 |
578 |
markom |
Tk 8.0.4 for Windows
|
2 |
|
|
|
3 |
|
|
by Scott Stanton
|
4 |
|
|
Scriptics Corporation
|
5 |
|
|
scott.stanton@scriptics.com
|
6 |
|
|
|
7 |
|
|
RCS: @(#) $Id: README,v 1.1.1.1 2002-01-16 10:26:02 markom Exp $
|
8 |
|
|
|
9 |
|
|
1. Introduction
|
10 |
|
|
---------------
|
11 |
|
|
|
12 |
|
|
This is the directory where you configure and compile the Windows
|
13 |
|
|
version of Tk. This directory also contains source files for Tk
|
14 |
|
|
that are specific to Microsoft Windows. The rest of this file
|
15 |
|
|
contains information specific to the Windows version of Tk.
|
16 |
|
|
|
17 |
|
|
2. Distribution notes
|
18 |
|
|
---------------------
|
19 |
|
|
|
20 |
|
|
Tk 8.0 for Windows is distributed in binary form in addition to the
|
21 |
|
|
common source release. The binary distribution is a self-extracting
|
22 |
|
|
archive with a built-in installation script.
|
23 |
|
|
|
24 |
|
|
Look for the binary release in the same location as the source release
|
25 |
|
|
(ftp.scriptics.com:/pub/tcl/tcl8_0 or any of the mirror sites). For most users,
|
26 |
|
|
the binary release will be much easier to install and use. You only
|
27 |
|
|
need the source release if you plan to modify the core of Tcl, or if
|
28 |
|
|
you need to compile with a different compiler. With the addition of
|
29 |
|
|
the dynamic loading interface, it is no longer necessary to have the
|
30 |
|
|
source distribution in order to build and use extensions.
|
31 |
|
|
|
32 |
|
|
3. Compiling Tk
|
33 |
|
|
----------------
|
34 |
|
|
|
35 |
|
|
In order to compile Tk for Windows, you need the following items:
|
36 |
|
|
|
37 |
|
|
Tcl 8.0 Source Distribution (plus any patches)
|
38 |
|
|
Tk 8.0 Source Distribution (plus any patches)
|
39 |
|
|
|
40 |
|
|
The latest Win32 SDK header files
|
41 |
|
|
|
42 |
|
|
Borland C++ 4.5 or later (32-bit compiler)
|
43 |
|
|
or
|
44 |
|
|
Visual C++ 2.x or later
|
45 |
|
|
|
46 |
|
|
In practice, 8.0.4 was built with Visual C++ 5.0
|
47 |
|
|
|
48 |
|
|
In the "win" subdirectory of the source release, you will find two
|
49 |
|
|
files called "makefile.bc" and "makefile.vc". These are the makefiles
|
50 |
|
|
for the Borland and Visual C++ compilers respectively. You should
|
51 |
|
|
copy the appropriate one to "makefile" and update the paths at the top
|
52 |
|
|
of the file to reflect your system configuration. Now you can use
|
53 |
|
|
"make" (or "nmake" for VC++) to build the tk libraries and the wish
|
54 |
|
|
executable.
|
55 |
|
|
|
56 |
|
|
In order to use the binaries generated by these makefiles, you will
|
57 |
|
|
need to place the Tk script library files someplace where Tk can
|
58 |
|
|
find them. Tk looks in one of two places for the library files:
|
59 |
|
|
|
60 |
|
|
1) The environment variable "TK_LIBRARY".
|
61 |
|
|
|
62 |
|
|
2) In the lib\tk8.0 directory under the Tcl installation directory
|
63 |
|
|
as specified in the registry:
|
64 |
|
|
|
65 |
|
|
For Windows NT & 95:
|
66 |
|
|
HKEY_LOCAL_MACHINE\SOFTWARE\Scriptics\Tcl\8.0
|
67 |
|
|
Value Name is "Root"
|
68 |
|
|
|
69 |
|
|
For Win32s:
|
70 |
|
|
HKEY_CLASSES_ROOT\SOFTWARE\Scriptics\Tcl\8.0\
|
71 |
|
|
|
72 |
|
|
2) Relative to the directory containing the current .exe.
|
73 |
|
|
Tk will look for a directory "..\lib\tk8.0" relative to the
|
74 |
|
|
directory containing the currently running .exe.
|
75 |
|
|
|
76 |
|
|
Note that in order to run wish80.exe, you must ensure that tcl80.dll,
|
77 |
|
|
tclpip80.dll (plus tcl1680.dll under Win32s), and tk80.dll are on your
|
78 |
|
|
path, in the system directory, or in the directory containing
|
79 |
|
|
wish80.exe.
|
80 |
|
|
|
81 |
|
|
4. Test suite
|
82 |
|
|
-------------
|
83 |
|
|
|
84 |
|
|
The Windows version of Tk does not pass many of the tests in the test
|
85 |
|
|
suite. This is primarily due to dependencies in the test suite on the
|
86 |
|
|
size of particular X fonts, and other X related features as well as
|
87 |
|
|
problems with "exec". We will be working to develop a more general
|
88 |
|
|
test suite for Tk under Windows, but for now, you will not be able to
|
89 |
|
|
pass many of the tests.
|
90 |
|
|
|
91 |
|
|
5. Known Bugs
|
92 |
|
|
-------------
|
93 |
|
|
|
94 |
|
|
Here is the current list of known bugs/missing features for the
|
95 |
|
|
Windows beta version of Tk:
|
96 |
|
|
|
97 |
|
|
- There is no support for custom cursors/application icons. The core
|
98 |
|
|
set of X cursors is supported, although you cannot change their color.
|
99 |
|
|
- Stippling of arcs isn't implemented yet.
|
100 |
|
|
- Some "wm" functions don't map to Windows and aren't implemented;
|
101 |
|
|
others should map, but just aren't implemented. The worst offenders
|
102 |
|
|
are the icon manipulation routines.
|
103 |
|
|
- Under Win32s, you can only start one instance of Wish at a time.
|
104 |
|
|
- Color management on some displays doesn't work properly resulting in
|
105 |
|
|
Tk switching to monochrome mode.
|
106 |
|
|
- Tk seems to fail to draw anything on some Matrox Millenium cards.
|
107 |
|
|
- Printing does not work for images (e.g. GIF) on a canvas.
|
108 |
|
|
- Tk_dialog appears in the upper left corner. This is a symptom of a
|
109 |
|
|
larger problem with "wm geometry" when applied to unmapped or
|
110 |
|
|
iconified windows.
|
111 |
|
|
- Some keys don't work on international keyboards.
|
112 |
|
|
- PPM images are using the wrong translation mode for writing to
|
113 |
|
|
files, resulting in CR/LF terminated PPM files.
|
114 |
|
|
- Tk crashes if the display depth changes while it is running. Tk
|
115 |
|
|
also doesn't consistently track changes in the system colors.
|
116 |
|
|
|
117 |
|
|
If you have comments or bug reports for the Windows version of Tk,
|
118 |
|
|
please direct them to:
|
119 |
|
|
|
120 |
|
|
|
121 |
|
|
|
122 |
|
|
or post them to the newsgroup comp.lang.tcl.
|