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