| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
| |
We will need many other forms of isolation for these. For starters we're
going to have to replace most asserts with warnings that can be traced
so that the environment doesn't crash because of illegal code typed into
it.
New test is still failing. Just getting it to fail right was hard
enough.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Focus on the one programming environment from now on: edit.mu. First get
it to print results of computations like repl does, then pipe warnings
into the environment somehow.
|
| |
|
|
|
|
|
| |
'run-interactive' now takes a string as input and returns a string as
output when it generates a result. As a result we also don't have to
worry about manual tests anymore, and it should now be reusable in
edit.mu.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Don't render all the editors on every single keystroke, render just the
one that was modified.
This will also be useful for our next step: heterogeneous editor widgets
responsible for their areas of screen and doing their own rendering and
responding to events.
|
| | |
|
| |
|
|
| |
Less objectionable placeholder for syntax highlighting mu fragments.
|
| | |
|
| |
|
|
| |
The menu bar needs separate recipes to render and respond to events.
|
| |
|
|
|
| |
Of course, editors might begin below other editors; this is a stopgap
solution. Yagni, yagni, yagni.
|
| |
|
|
|
| |
More sketching out of a bare-bones scenario. What should happen when we
press F9? Print a result somewhere?
|
| |
|
|
|
|
| |
Simpler gradient computation.
But in the end it looks better when the gradient is so subtle as to be
irrelevant. Might as well eliminate the gradient altogether.
|
| |
|
|
| |
But integer division is a fail, as expected.
|
| | |
|
| | |
|
| | |
|
| | |
|