Geoffrey Broadwell

Xliff: This is something I had planned to take a look at as I worked a bit more on the high-level widget support code. That work had been blocked on...

Sure, flood fill is pretty much a requirement, but it's inefficient if e.g. you just want to display simple polygons or elliptical arcs for e.g. pie charts.

Spent some time investigating mouse input. Turns out there are a number of different mouse event protocols that have been supported by various terminal emulators over the years, with various...

The input system will be more useful proper event bubbling, not just delivering all inputs to one place and forcing the app author to demux the input. This may be...

I've started sketching out raw input on the (rather obviously named) raw-input branch. There are known problems with the implementation (not least that currently I can't convert escape sequences into...

With some clarification from jnthn++ in https://rt.perl.org/Public/Bug/Display.html?id=130716 , I've made some progress in the raw-input branch. The current structure should be more friendly to making a special key decoding layer,...

Update: In current Rakudo, `examples/tris.p6` (still on the raw-input branch) works just fine, it's just stuck using normal printable character keys for input because there's not yet any escape sequence...

I've merged raw-input because it seemed quite stable, and have locally started a new branch (decode-keys) for writing the key-decoding logic. Turns out the escape sequence parser I found in...

Well, I've now got a rough start working: https://github.com/ab5tract/Terminal-Print/blob/decode-keys/lib/Terminal/Print/DecodedInput.pm6 . It only decodes the four cursor directional keys, it doesn't know how to handle hitting the escape key by itself...

OK, that should be a mapping for all remaining special keys defined by xterm except Escape itself and the various modifiers; as a bonus I've added the Bracketed Paste markers...