eliminate printStackTrace() in example

[nikiroo-utils.git] / README.md

diff --git a/README.md b/README.md
index db12ef6f58d44c8a5d77f1430c11f8ed2325e96c..2a62f1c1eb6531b151b60b6aec531883b5e10593 100644 (file)
--- a/README.md
+++ b/README.md
@@ -48,6 +48,20 @@ This project is licensed under the MIT License.  See the file LICENSE
 for the full license text.
 
 
+Maven
+-----
+
+Jexer is available on Maven Central:
+
+```xml
+<dependency>
+  <groupId>com.gitlab.klamonte</groupId>
+  <artifactId>jexer</artifactId>
+  <version>0.3.0</version>
+</dependency>
+```
+
+
 
 Acknowledgements
 ----------------
@@ -79,13 +93,9 @@ class MyApplication extends TApplication {
         new MyWindow(this);
     }
 
-    public static void main(String [] args) {
-        try {
-            MyApplication app = new MyApplication();
-            (new Thread(app)).start();
-        } catch (Throwable t) {
-            t.printStackTrace();
-        }
+    public static void main(String [] args) throws Exception {
+        MyApplication app = new MyApplication();
+        (new Thread(app)).start();
     }
 }
 ```
@@ -154,9 +164,9 @@ follows:
   * '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 one
-    application performing I/O to two screens: an xterm screen and a
-    Swing screen.
+  * '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.
 
 
 
@@ -329,8 +339,7 @@ Some of the areas that will likely require significant efforts are:
     syntax or at least regexp highlighting (not just keywords), paren
     matching, paragraph/comment reflow, and dozens more.  The
     underlying Document/Line/Word model is not going to be sufficient
-    to meet these features.  It would be up to you if you wish to
-    retrofit any improvements you make to the MIT version of Jexer.
+    to meet these features.
 
   * Better Windows and OSX support.  It would be nice to ship a
     jlink'ed JVM on these platforms with the JRE, JDK, and JPDA
@@ -338,25 +347,13 @@ Some of the areas that will likely require significant efforts are:
     consider doing any of the following: ship a third-party terminal,
     use PowerShell, or use the newer ConPTY for TTerminalWindow.
 
-  * Project window awareness for modules.  Currently the project
-    window knows only simple file paths (where it assumes paths are
-    subpackages) and jars.  It would be nice to also have module
-    awareness here, since modules are the future for Java.
-
-  * Bug fixes.  The (G)Jexer codebase is quite large despite my best
+  * Bug fixes.  The Jexer codebase is quite large despite my best
     efforts.  Bugs are typically very small to fix, but can take some
     time to find: a simple NPE or AssertionError can sometimes take
     4-8 hours to squash.  Fortunately, fixing issues in one place has
     not often led to breakages elsewhere.
 
-  * Plugin support.  TJIDE is the first truly new TUI-based IDE to
-    emerge in quite some time.  It was deliberately built to resemble
-    IDEs used to teach computer science courses for decades, and it is
-    hoped that instructors will be able to use it soon.  A plugin
-    system to define new kinds of targets, editors, and debuggers
-    would go a long way to using TJIDE for other languages.
-
-  * New (G)Jexer applications.  So far as I know, (G)Jexer is the only
+  * New Jexer applications.  So far as I know, Jexer is the only
     mouse-supporting full TUI windowing framework with sixel image
     support in existence.  I cannot predict what kinds of applications
     could be built out of it, and how those needs will push back to
@@ -365,10 +362,10 @@ Some of the areas that will likely require significant efforts are:
 These are what I can clearly see right now.  Obviously users are
 capable of finding many more.
 
-I intend to continue poking on TJIDE and Jexer, and will maintain a
+I intend to continue poking on Jexer and TJIDE, and will maintain a
 branch to be "the fastest and simplest Java language IDE available",
 which will deliberately remain small.
 
-I hope that other languages choose to transliterate MIT Jexer to
-provide TUIs to their own platforms.  I will be happy to help them
-understand the code to support those efforts.
+I hope that other languages choose to transliterate Jexer to provide
+TUIs to their own platforms.  I will be happy to help them understand
+the code to support those efforts.