+![The Example Code Above](/screenshots/readme_application.png?raw=true "The application in the text of README.md")
+
+
+
+More Examples
+-------------
+
+The examples/ folder currently contains:
+
+ * A [prototype tiling window
+ manager](/examples/JexerTilingWindowManager.java) in less than 250
+ lines of code.
+
+ * A [prototype image thumbnail
+ viewer](/examples/JexerImageViewer.java) in less than 350 lines of
+ code.
+
+jexer.demos contains official demos showing all of the existing UI
+controls. The demos can be run as follows:
+
+ * 'java -jar jexer.jar' . This will use System.in/out with
+ xterm-like sequences on non-Windows non-Mac platforms. On Windows
+ and Mac it will use a Swing JFrame.
+
+ * 'java -Djexer.Swing=true -jar jexer.jar' . This will always use
+ Swing on any platform.
+
+ * 'java -cp jexer.jar jexer.demos.Demo2 PORT' (where PORT is a
+ number to run the TCP daemon on). This will use the telnet
+ protocol to establish an 8-bit clean channel and be aware of
+ screen size changes.
+
+ * 'java -cp jexer.jar jexer.demos.Demo3' . This will use
+ System.in/out with xterm-like sequences. One can see in the code
+ how to pass a different InputReader and OutputReader to
+ TApplication, permitting a different encoding than UTF-8.
+
+ * 'java -cp jexer.jar jexer.demos.Demo4' . This demonstrates hidden
+ windows and a custom TDesktop.
+
+ * 'java -cp jexer.jar jexer.demos.Demo5' . This demonstrates two
+ demo applications using different fonts in the same Swing frame.
+
+ * 'java -cp jexer.jar jexer.demos.Demo6' . This demonstrates two
+ applications performing I/O across three screens: an xterm screen
+ and Swing screen, monitored from a third Swing screen.
+
+
+
+More Screenshots
+----------------
+
+![Several Windows Open Including A Terminal](/screenshots/screenshot1.png?raw=true "Several Windows Open Including A Terminal")
+
+![Yo Dawg...](/screenshots/yodawg.png?raw=true "Yo Dawg, I heard you like text windowing systems, so I ran a text windowing system inside your text windowing system so you can have a terminal in your terminal.")
+
+![Sixel Pictures Of Cliffs Of Moher And Buoy](/screenshots/sixel_images.png?raw=true "Sixel Pictures Of Cliffs Of Moher And Buoy")
+
+![Sixel Color Wheel](/screenshots/sixel_color_wheel.png?raw=true "Sixel Color Wheel")
+
+
+Terminal Support
+----------------
+
+The table below lists terminals tested against Jexer's ECMA48/Xterm
+backend.
+
+| Terminal | Environment | Mouse Click | Mouse Cursor | Images |
+| -------------- | ------------------ | ----------- | ------------ | ------ |
+| xterm | X11 | yes | yes | yes |
+| lcxterm | CLI, Linux console | yes | yes | no |
+| rxvt-unicode | X11 | yes | yes | no |
+| alacritty(3) | X11 | yes | yes | no |
+| gnome-terminal | X11 | yes | yes | no |
+| xfce4-terminal | X11 | yes | yes | no |
+| aminal(3) | X11 | yes | no | no |
+| konsole | X11 | yes | no | no |
+| yakuake | X11 | yes | no | no |
+| screen | CLI | no(1) | no | no(2) |
+| tmux | CLI | no(1) | no | no |
+| putty | X11, Windows | yes | no | no(2) |
+| Linux | Linux console | no | no | no(2) |
+| qodem(3) | CLI, Linux console | yes | yes(4) | no |
+| qodem-x11(3) | CLI | yes | no | no |
+
+1 - Passes mouse to its host console, so will support mouse if the
+host console does.
+
+2 - Also fails to filter out sixel data, leaving garbage on screen.
+
+3 - Latest in repository.
+
+4 - Requires TERM=xterm-1003 before starting.
+
+
+
+System Properties
+-----------------
+
+The following properties control features of Jexer:
+
+ jexer.Swing
+ -----------
+
+ Used only by jexer.demos.Demo1 and jexer.demos.Demo4. If true, use
+ the Swing interface for the demo application. Default: true on
+ Windows (os.name starts with "Windows") and Mac (os.name starts with
+ "Mac"), false on non-Windows and non-Mac platforms.
+
+ jexer.Swing.cursorStyle
+ -----------------------
+
+ Used by jexer.backend.SwingTerminal. Selects the cursor style to
+ draw. Valid values are: underline, block, outline. Default:
+ underline.
+
+ jexer.Swing.tripleBuffer
+ ------------------------
+
+ Used by jexer.backend.SwingTerminal. If true, use triple-buffering
+ which reduces screen tearing but may also be slower to draw on
+ slower systems. If false, use naive Swing thread drawing, which may
+ be faster on slower systems but also more likely to have screen
+ tearing. Default: true.
+
+ jexer.TTerminal.ptypipe
+ -----------------------
+
+ Used by jexer.TTerminalWindow. If true, spawn shell using the
+ 'ptypipe' utility rather than 'script'. This permits terminals to
+ resize with the window. ptypipe is a separate C language utility,
+ available at https://gitlab.com/klamonte/ptypipe. Default: false.
+
+ jexer.TTerminal.closeOnExit
+ ---------------------------
+
+ Used by jexer.TTerminalWindow. If true, close the window when the
+ spawned shell exits. Default: false.
+
+ jexer.ECMA48.rgbColor
+ ---------------------
+
+ Used by jexer.backend.ECMA48Terminal. If true, emit T.416-style RGB
+ colors for normal system colors. This is expensive in bandwidth,
+ and potentially terrible looking for non-xterms. Default: false.
+
+ jexer.ECMA48.sixel
+ ------------------
+
+ Used by jexer.backend.ECMA48Terminal. If true, emit image data
+ using sixel, otherwise show blank cells where images could be. This
+ is expensive in bandwidth, very expensive in CPU (especially for
+ large images), and will leave artifacts on the screen if the
+ terminal does not support sixel. Default: true.
+
+
+
+Known Issues / Arbitrary Decisions
+----------------------------------
+
+Some arbitrary design decisions had to be made when either the
+obviously expected behavior did not happen or when a specification was
+ambiguous. This section describes such issues.
+
+ - See jexer.tterminal.ECMA48 for more specifics of terminal
+ emulation limitations.
+
+ - TTerminalWindow uses cmd.exe on Windows. Output will not be seen
+ until enter is pressed, due to cmd.exe's use of line-oriented
+ input (see the ENABLE_LINE_INPUT flag for GetConsoleMode() and
+ SetConsoleMode()).
+
+ - TTerminalWindow by default launches 'script -fqe /dev/null' or
+ 'script -q -F /dev/null' on non-Windows platforms. This is a
+ workaround for the C library behavior of checking for a tty:
+ script launches $SHELL in a pseudo-tty. This works on Linux and
+ Mac but might not on other Posix-y platforms.
+
+ - Closing a TTerminalWindow without exiting the process inside it
+ may result in a zombie 'script' process.
+
+ - When using the Swing backend, and not using 'ptypipe', closing a
+ TTerminalWindow without exiting the process inside it may result
+ in a SIGTERM to the JVM causing it to crash. The root cause is
+ currently unknown, but is potentially a bug in more recent
+ releases of the 'script' utility from the util-linux package.
+
+ - TTerminalWindow can only notify the child process of changes in
+ window size if using the 'ptypipe' utility, due to Java's lack of
+ support for forkpty() and similar. ptypipe is available at
+ https://gitlab.com/klamonte/ptypipe.