6
Much of the XMLterm code is cross-platform. Implementation features that
7
affect portability at the moment are:
9
1. Main event handling:
10
By default, the present implementation of XMLterm directly uses a GTK
11
call to set up a handler for XMLterm output events. This can be disabled
12
by setting NO_CALLBACK=1 in the make command line, and calling the
13
method mozIXMLTermShell::Poll() frequently to poll for readable output
15
(A better event/callback mechanism needs to be implemented.)
17
2. pseudo-TTY (PTY) operations:
18
The PTY interface for XMLterm is currently implemented only for
19
two platforms, Linux and Solaris. At some point, the PTY interface
20
should be ported to most Unix platforms. On platforms where PTY
21
operations are not implemented, the cross-platform NSPR process mechanism
22
is used to create a "slave" process. However, this process uses NSPR
23
pipes for communication, which prevents the use of terminal control
24
characters such as the most usefule Control-C. (Is there a way around
27
What about Windows? It should be possible to use XMLterm even under Windows,
28
using the NSPR process/pipe functions for communication and
29
using the Cygwin utilities to simulate the Unix environment.
31
3. The lightweight GeckoTerm uses GTK.
33
4. The "unistring" module uses wchar functions which do not always have