pjs/xmlterm в 8e5c7532684769b24bd892c5b828eca3122f557d - pjs

История

blizzard%redhat.com 8ec176345e Change nsComponentManager::ProgIDToCLSID to nsComponentManager::ProgIDToClassID as per bug #3579 . Checking in for sford. r=scc,r=blizzard		1999-12-30 22:03:58 +00:00
..
base	Change nsComponentManager::ProgIDToCLSID to nsComponentManager::ProgIDToClassID as per bug #3579 . Checking in for sford. r=scc,r=blizzard	1999-12-30 22:03:58 +00:00
config	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
dist	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
doc	NOT PART OF SEAMONKEY BUILD;	1999-12-26 15:19:45 +00:00
geckoterm	NOT PART OF SEAMONKEY BUILD;	1999-12-26 15:19:45 +00:00
linetest	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
tests	NOT PART OF SEAMONKEY BUILD;	1999-12-26 15:19:45 +00:00
ui	NOT PART OF SEAMONKEY BUILD;	1999-12-26 15:19:45 +00:00
.cvsignore	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
INSTALL	XMLterm changes; NOT PART OF SEAMONKEY BUILD; fixed Solaris bug in makemake;	1999-12-08 02:55:56 +00:00
Makefile.in	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
README	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
UUID.txt	Initial import of XMLterm extension; not part of default SeaMonkey build	1999-12-06 06:32:12 +00:00
makemake	XMLterm changes; NOT PART OF SEAMONKEY BUILD; fixed Solaris bug in makemake;	1999-12-08 02:55:56 +00:00

README

xmlterm --- A graphical command line interface
==============================================

An early prototype of XMLterm, an XTERM-like terminal program implemented
using the open source Mozilla layout engine, is now available to tinker
with. XMLterm aims to add graphical and hypertext capabilities to the XTERM
command line interface, while maintaining backwards compatibility.

The basic design philosophy of XMLterm is that the user interface is a dynamic
XML document. The user and the computer interact by taking turns at appending
to this XML document. The plain text content of the XML document, i.e.,
excluding any markup, corresponds to the plain text that would be displayed by
a plain XTERM. The markup in the XML document is used to add graphical and
hypertext features. XMLterm uses the Mozilla layout engine to display the XML
document.

XMLterm is an open source project in its early stages. Comments and
contributions are welcome!

R. Saravanan <svn@xmlterm.org>
28 Nov 1999
===========

NOTES:

 1. See the INSTALL file for configuration/installation instructions.

 2. See the file doc/INSTALL.xmlterm for binary installation instructions.

 3. Check the XMLterm web site <http://xmlterm.org> for updates.

===========================================================================
DOCUMENTATION

 a. There is a README file in each directory that provides some basic
    information.

 b. The file "base/README" provides a brief overview of the XMLterm code
    architecture.

 c. The header files (*.idl, *.h) have comments describing class methods
    and member variables in JAVADOC format. Look at them before delving
    into the *.cpp files

===========================================================================
FILES:

  INSTALL        installation instructions
  README         this file
  UUID.txt       list of UUIDs used by XMLterm

The main subdirectories of the "xmlterm" directory are:

  base/          base source code for XMLterm libraries
  config/        make rules for stand-alone mode
  dist/          holds include and library file for stand-alone LineTerm only
  doc/           some documentation
  geckoterm/     lightweight XMLterm executable
  linetest/      stand-alone line terminal testing executables
  tests/         XMLterm test programs and scripts, including "pagelets"
  ui/*           user interface/chrome files

--