| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
| |
We won't bother supporting names for globals, for now.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
As usual, trying to fix this manually was a false economy. Writing this
test in the first place would have made debugging much simpler.
|
| |
|
|
| |
Finally, albeit too late for my demo.
|
| | |
|
| |
|
|
| |
Quick hack for demo at balisp meetup today.
|
| |
|
|
| |
No idea why this was wrong, but whatever..
|
| |
|
|
|
|
|
|
|
| |
We're starting to hit the limits of my 8GB RAM, to the point where I'm
starting to economize on the size of the screen. Time to start thinking
about reclaiming memory.
Anyways, test now fails in the right place. I'm failing to propertly
render intermediate lines between sandboxes.
|
| | |
|
| |
|
|
| |
We're ready to start displaying multiple sandboxes.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Cleanup below editors is now all done.
|
| | |
|
| |
|
|
|
|
|
| |
Ah, I was indeed double-rendering, but somehow it was still hard to see
the problem past that preliminary diagnosis.
Still two failing tests to fix.
|
| |
|
|
|
| |
No, that's a false alarm. There's just a larger screen to manipulate.
But the size of the screen doesn't change in interactive mode.
|
| |
|
|
|
|
| |
Comparing trace counts for a single test before and after yesterday's
changes, one obvious culprit is that print-character has blown up from
754 trace lines (at all levels) to 2554.
|
| | |
|
| | |
|
| |
|
|
| |
$ ./mu test run-instruction-and-print-warnings
|
| |
|
|
|
|
|
|
|
|
| |
Still ugly as hell. Some tests failing, but they're most likely
wrong. We need to test cursor positioning at the level of the
environment and take it away from the responsibilities of individual
editors. Also bring back the line at the bottom of each editor.
The non-test run ('main' in edit.mu) is completely borked. Sluggish as
hell, and I can't seem to switch focus to the sandbox editor.
|
| |
|
|
|
| |
Current model: you click on something to put it on the editor at the top
of the column. Worth a shot.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
I probably need another test like editor-clears-last-line-on-backspace,
but we aren't testing the boundary, and we're pushing on anyway.
|
| |
|
|
| |
Leaves a line blank after printing result/warnings, for some reason.
|
| | |
|
| | |
|
| |
|
|
| |
All tests passing, but early layers are broken.
|
| |
|
|
|
|
| |
Hmm, this is undesirable, that recipes don't need to explicitly reply.
Need to fix. Also need to have run-interactive create scenarios at some
point.
|
| |
|
|
| |
Pushing back some of the weight of repetitive boilerplate.
|
| |
|
|
|
| |
This is starting to look good! I need to add some tests for
render-string, but we'll see.
|
| | |
|
| |
|
|
| |
The trick is to check for more events and not bother rendering if so.
|
| |
|
|
| |
Switch to F10 because F9 is in use under my setup.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Some reorg before we start plumbing 'reply' from 'run-interactive' to
return a string containing the results.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Also added another failing test showing what behavior we want in the
programming environment. But there's no way to make use of querying
locations, since we're not planning any interaction with individual
sandboxes at the moment.
Instead of interacting with one sandbox at a time, which is the current
approach, we want to create dashboards out of multiple sandboxes at
once. Start with them non-interactive, that'll demonstrate 80% of the
new benefits. We'll add interactivity down the road.
|