new (last?) Kawa binary pre-release

[Per Bothner <per at bothner dot com>]

Grab it as usual from ftp://ftp.gnu.org/pub/gnu/kawa/kawa-latest.zip .

This is basically a release candidate, except for the version number.

* The -w option now takes various sub-options.  For example
-wbrowser creates a server (two actually: http and WebSocket),
and then pops up a REPL window in the your default web browser.

-wswing is the old Swing console and -wjavafx is the new JacaFX+DomTerm one.
Plain -w tries various options in order - see the manual for the gory details.

* A new --browse-manual option for (you guessed it) browsing the
(included) manual.  This has various sub-options; the default
creates a new window in your default browser.

* The browse-kana-manual command has been removed. It handled
external links poorly (replacing the entire window), and fixing
it didn't seem a priority.  (It's still in the Subversion source,
but now in the doc directory.)

* The new -w option(s) now works on plain Windows 10.  Even with DomTerm
and JLine3 line editing; composable pictures output etc.
--browse-manual also works.  The bin/kawa shell script works on MinGW.

* On DomTerm the default prompt emits hide/show buttons.

On 11/02/2016 03:58 PM, Per Bothner wrote:
> (I'm considering adding a function that starts a http
> server, and then uses the Desktop class to create a browser
> window.  The tricky part is shutting down the server when the
> window is closed.  Let me know if that would be helpful.
> The function could be called from your own code, or from the
> Kawa command-line.)

Did that ...

> The JaveFX-based console does have some blemishes.  Obviously,
> it requires JavaFX and specifically WebView, which are not getting
> a lot of love from Oracle.  Copy/Paste are flaky.  I'm considering
> prioritizing a browser-based console.  The -w flag would (by default)
> start a small web-server (including WebSockets), and then start up
> a DomTerm window in your preferred browser.  What do you think?
> Most of what's needed is already implemented in Kawa or DomTerm;
> it's just a matter of putting them together.  (I think it can be done
> without PTYs or native code, which is obviously a plus.)

Did that - in spades ...

--
	--Per Bothner
per@bothner.com   http://per.bothner.com/