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
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
|
-- $Id$
SHORT-TERM TO-DO ITEMS:
Known Problems:
* GNAT does not put libraries in the correct order, so a build only links
properly if you use shared libraries since -lncurses is first.
* The screen optimization has been tested only in an ad hoc manner. We should
develop a good set of regression tests to cover lib_doupdate.c and
lib_mvcur.c.
* Magic cookie support does not work, since the logic does not take into account
refresh. Also, the initial optimize does not adjust the current location
when a cookie is emitted.
* Scrolling optimization has holes: for example, it forces repaints of the
screen between calls to refresh().
* SVr4 uses slightly different rules for determining when softkeys are shown.
For example, they are initially displayed (before the ncurses 'e' test
activates them), and a touchwin can apparently also force them to be
displayed.
+ The code departs from perfect 8-bit cleanness in one respect; you cannot
specify a character \200 as part of a capability string, because the terminfo
library interprets \200 as a request to embed NUL (\000) at that point. This
is a legacy terminfo property we can't mess with.
* The window classes defined in the c++ subdirectory need documentation.
Some C++ programmer could earn a lot of good karma by doing this...
* The resizeterm() function does not handle ripped-off lines such as that
done for the slk_XXX functions.
Portability (or lack thereof):
* Users of older System V UNIXes (but not Solaris, and probably not SVr4)
may trip over a known problem with the signal-handling code which causes
abrupt termination of ncurses applications following resume from a ^Z
suspend (this problem was first seen running lynx). You will not see
this problem if you are running Linux or one of the 4.4BSD derivatives
like FreeBSD, NetBSD, or BSDI. For details, see the analysis in the
header comment of ncurses/lib_tstp.c.
* In theory, vwprintw and vwscanf are supposed to use the older varargs.h
interface for handling variadic argument lists. Linux doesn't have
varargs.h, it has the newer X/Open-standard stdargs.h equivalent. So
these functions use stdargs instead. This is unlikely to be a problem
unless you're building ncurses on a System V old enough to only have
varargs.h. (Solaris 2.5.1 uses the stdarg.h binding as well).
* If you're using a BSD earlier than 4.4BSD, or a Linux old enough not to
have a native vsscanf(3) in its library, vwscanw() will not work. You lose.
(It should work on any System V, however). If you want to fix this, add
an implementation to ncurses/vsscanf.c.
* The demo build for the c++ library craps out with many link errors under gcc
2.6.3. We're told the C++ support in 2.6.3 is broken and that the right
fix is to upgrade to 2.7.0. This demo is also known to not build with
the Sun SPARCworks 4.1 C++ compiler, due to a problem resolving templates.
* Under Ultrix, configure craps out (Ultrix sh is lame). Run it under ksh.
* We've not tested the configure script with cross-compilers. The autoconf
tests are supposed to be able to support this (please report bugs). You will
have to configure and build in two steps. The first step must create the
automatically-generated sources (e.g., comp_captab.c) on your host machine.
Then, run "make mostlyclean", remove config.* from the top-level directory
and configure for the cross-compiler.
+ terminfo.5 does not format with the SunOS (and most other platform's) tbl
utility because it relies on a diversion for each table entry. Get the groff
package.
Untested features:
* The code for the HP color model using set_color_pair is untested.
* The code for handling soft labels on a terminal type with built-in support
for them (num_labels > 0, label_height, label_width, label_format, label_off,
label_on, plab_norm, lab_f*) has not been tested. The label_format and
lab_f* capabilities aren't presently used.
* The wide-character input functions need testing.
LONGER-TERM TO-DO ITEMS:
1. Extended COSE conformance
There is an XPG4 standard recently released which describes a superset
of the SVr4 API. The library is BASE conformant with this standard.
We would like to make ncurses fully conformant at the EXTENDED level
supporting internationalization.
Current status:
pecho_wchar() not implemented.
slk_wset not implemented.
2. DOS port
Only 16 of the 55 files in the library depend on the terminfo format.
It should be possible to further kernelize the package, then rewrite
a small number of core files to produce a functionally-compatible
port that would do updates to a memory-mapped screen area. The first
result of this would be a DOS port.
3. X port
It would be nice if ncurses could recognize when it was running under X and
maintain its own window. With this feature, all ncurses programs would
automatically become X programs. The challenge is to handle resize events
properly.
4. Unused capabilities
The currently unused capabilities fall naturally into several groups:
A. Status-line capabilities:
Booleans: has_status_line, status_line_esc_ok.
Numerics: width_status_line.
Strings: dis_status_line, from_status_line, to_status_line.
System V Release 1 curses made no use of these at all. SVr4's use, if
any, is unknown. From the AT&T termcap file it looks like curses, in general,
shouldn't use them; terminal variants with status lines have their line count
decremented by 1, suggesting that curses is supposed to leave the status line
alone.
B. Printer capabilities:
Boolean: col_addr_glitch, cr_cancels_micro_mode, has_print_wheel,
row_addr_glitch, semi_auto_right_margin, cpi_changes_res,
lpi_changes_res.
Numeric: buffer_capacity, dot_horz_spacing, dot_vert_spacing,
max_micro_address, max_micro_jump, micro_col_size,
micro_line_size, number_of_pins, output_res_char,
output_res_line, output_res_horz_inch, print_rate,
wide_char_size, bit_image_entwining, bit_image_type.
String: down_half_line, form_feed, up_half_line, set_left_margin,
set_right_margin, clear_margins, change_char_pitch
... set_page_length (all the SVr4 printer caps),
Curses doesn't use these.
C. Printer-control capabilities:
Boolean: prtr_silent.
Strings: print_screen, prtr_on, prtr_off, prtr_non.
Curses doesn't use these.
D. Dialer strings:
Strings: hangup, dial_phone, quick_dial, tone, pulse, flash_hook,
fixed_pause, wait_tone.
Curses doesn't use these.
E. Window and virtual-terminal capabilities:
Numerics: maximum_windows, virtual_terminal.
Strings: req_for_input, create_window, goto_window, set_window.
These seem to be fossils from some AT&T experiments on character-based
window systems that never escaped the lab. The virtual_terminal cap had
something to do with building terminal emulations into tty line disciplines.
F. Unused VDT capabilities:
Booleans: erase_overstrike, has_meta_key, insert_null_glitch,
move_insert, dest_tabs_magic_smso, transparent_underline,
needs_xon_xoff, hard_cursor.
Numerics: lines_of_memory, buttons.
Strings: pkey_key, pkey_local, pkey_xmit, underline_char,
enter_xon_mode, exit_xon_mode, xon_character, xoff_character,
display_clock, remove_clock, user[0-5], display_pc_char,
enter_scancode_mode, exit_scancode_mode, pc_term_options,
scancode_escape, alt_scancode_esc.
These are the potentially important ones for ncurses. Notes:
i) ncurses doesn't need move_insert; it never uses cup/hpa/vpa while
insert_mode is on.
ii) We probably don't care about dest_tabs_magic_smso; only
Telerays used it and they're all long obsolete.
|
