| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Bug in manually running editor. Why wasn't it uncovered in the test?
Because I'm not yet rendering again from the event loop.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Old plan: deduce cursor-row/column based on cursor.
New plan: deduce cursor based on cursor-row/column.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Html is a little more readable thanks to feedback from J David Eisenberg
(https://news.ycombinator.com/item?id=9766330), in particular the
suggestion to use https://addons.mozilla.org/En-us/firefox/addon/wcag-contrast-checker.
|
| |
|
|
|
|
|
|
| |
This takes away the need for multi-level escaping in scenario setup.
Post-conditions like screen-should-contain are still an issue, though.
Maybe each string literal should be able to specify escapes inside its
syntax? Or at a per-instruction granularity?
|
| | |
|
| | |
|
| |
|
|
|
|
| |
First, undo our existing hacky pseudo-support.
Some repl tests currently breaking.
|
| |
|
|
| |
But we certainly can't use it in the editor.
|
| | |
|
| |
|
|
|
|
| |
I still want to bring back replace-in-keyboard. No, not exactly that.
But saying press 8, press 8, press 8, over and over again, that's a
pain.
|
| | |
|
| |
|
|
|
|
|
| |
But still feels rough:
Variable names are still funky: 'k' and 'm'.
Field names still not copacetic: single-touch-event. Foolish
consistencies..
|
| |
|
|
|
|
|
|
| |
repl.mu now passing again. But still I have concerns:
a) Doubling backslashes in tests. Hard to tell how many levels to add.
b) I think the read-key interface needs to go. But then how do we handle
send-keys-to-channel and other flows like that in the chessboard app?
|
| |
|
|
|
|
|
|
| |
chessboard finally passing all its tests. What made this hard was that
for some reason one of the background routines in the main chessboard
test wasn't terminating like it used to. And so it was polluting *later*
tests. Just clean up that source of contamination for now. Later we'll
think about routine termination.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Only core layers currently passing. Console apps are probably still
broken.
|
| | |
|
| | |
|
| |
|
|
| |
No way to quit yet, though.
|
| | |
|
| | |
|
| |
|
|
| |
Reorg.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Rip out keyboard for now, add notion of cursor.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
More editor experiments.
a) I'm starting out with just a doubly linked list of characters as the
editor data structure. Haven't actually started using it yet.
b) Rather than provide a top-left-bottom-right bounding box up front, I
think I want to allow the bounding box to flow indefinitely down given
top, left and right. The old approach mimics traditional windowing
systems, while the new one mimics html flowing; I want a single
scrollbar for all my rendered elements within a single column.
|
| | |
|
| | |
|
| |
|
|
|
| |
I forgot to check for nulls before writing prev pointers in doubly
linked lists. Tests were accidentally passing.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Some tests weren't actually running for the past 5 days.
Performed 5 why's.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
This uncovers an issue with this interface to duplex lists: the caller
needs to check the result and invalidate any other pointers if it's null
(i.e. the list is now empty)
We *could* try to encapsulate the list in a header to help the caller
manage header pointers. But heck, let's see if writing tests helps
call-sites stay on the straight and narrow.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|