From: Charlie Turner <chturne@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: Kawa mailing list <kawa@sourceware.org>
Subject: Re: DomTerm - a new console for Kawa (and everyone else)
Date: Fri, 18 Dec 2015 18:43:00 -0000 [thread overview]
Message-ID: <CAPMhJv2OYR9FaoGPNgzOdo6RcqRq_YpUgzYSkYeO=Hhgrdxe7A@mail.gmail.com> (raw)
In-Reply-To: <56733C82.1050008@bothner.com>
This looks really good. I was experimenting with a Kawa backend for
Geiser, but due to the way Geiser expects prompts to be redrawn, and
how Kawa redraws prompts, it seemed like a bit of non-starter (I can
go into a lot more detail on that).
Anyway, I think the move to a web-based console is the best thing to do as well.
What's the dependence on OpenJDK in particular? Would I be able to get
away with Oracle JDK? I'm currently on OSX, and not yet terrible
proficient with it; it seems like OpenJDK 1.8 and OSX isn't quite
supported, or at least binary packages aren't provided.
Looking forward to playing with this.
--Charlie.
On 17 December 2015 at 22:51, Per Bothner <per@bothner.com> wrote:
> Lately I've been quiet on the Kawa front because I've been spending
> my time on DomTerm, whose goal is a best-of-breed hybrid of
> xterm/ansi-compatible terminal emulator combined with a powerful REPL
> console supporting rich text, graphics. readline-style editing, and more.
> The core of the code is (semi-) portable and embeddable JavaScript.
>
> The home page is http://domterm.org/
> and the source code is https://github.com/PerBothner/DomTerm
>
> Form the Kawa point of view, note especially the 2nd screenshot of
> the Features page: http://domterm.org/Features.html . If you "print"
> an XML node value, then it is inserted as HTML in the DomTerm output.
> (This happens for display but not for write, obviously.)
>
> Kawa also supports different styles/colors for the prompt (default green),
> input (default blue), and error output (default red). This works whether
> you invoke Kawa from the shell (running under DomTerm), or have DomTerm
> start up kawa.repl.main directly.
>
> I also want to implement the "graphics objects" ideas supported by the
> Swing console (which I know is currently broken):
> http://per.bothner.com/blog/2007/ReplPane/
>
> I expect we'll change the -w option (or just entering a REPL when there is
> no console) so it starts up a DomTerm rather than the old Swing console.
> (Though I intend to keep the latter around for now - after I debug it.)
>
> More Lisp-IDE-type ideas are also being considered. For example being
> able to interrupt a running expression and see a stack trace. However,
> that may be a bit further off.
>
> This is still alpha quality, and the interfaces are highly unstable,
> if using Kawa with DomTerm, update both sources at the same time.
> Otherwise, have fun with it.
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
next prev parent reply other threads:[~2015-12-18 18:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 22:52 Per Bothner
2015-12-18 18:43 ` Charlie Turner [this message]
2015-12-18 19:14 ` Per Bothner
2015-12-18 19:28 ` Charlie Turner
2015-12-18 19:41 ` Jamison Hope
2015-12-18 19:46 ` Per Bothner
2015-12-18 20:00 ` Charlie Turner
2015-12-22 7:38 ` Per Bothner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPMhJv2OYR9FaoGPNgzOdo6RcqRq_YpUgzYSkYeO=Hhgrdxe7A@mail.gmail.com' \
--to=chturne@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).