about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* 1764 - editor now updates all sandboxesKartik K. Agaram2015-07-113-15/+61
| | | | Finally, albeit too late for my demo.
* 1763 - warn on break/loop outside {}Kartik K. Agaram2015-07-111-85/+54
|
* 1762 - numbers without types = literalsKartik K. Agaram2015-07-111-0/+4
| | | | Quick hack for demo at balisp meetup today.
* 1761 - multiple sandboxes seems to be workingKartik K. Agaram2015-07-111-1/+0
| | | | No idea why this was wrong, but whatever..
* 1760 - failing test for multiple sandboxesKartik K. Agaram2015-07-111-53/+76
| | | | | | | | | 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.
* 1759Kartik K. Agaram2015-07-112-2/+6
|
* 1758 - now clear sandbox editor on F10Kartik K. Agaram2015-07-111-13/+47
| | | | We're ready to start displaying multiple sandboxes.
* 1757Kartik K. Agaram2015-07-111-7/+12
|
* 1756Kartik K. Agaram2015-07-111-7/+19
|
* 1755Kartik K. Agaram2015-07-101-13/+13
|
* 1754Kartik K. Agaram2015-07-103-16/+19
|
* 1753 - all tests passing againKartik K. Agaram2015-07-101-41/+47
| | | | Cleanup below editors is now all done.
* 1752 - cursor positioning fixedKartik K. Agaram2015-07-101-6/+8
|
* 1751 - sluggishness fixedKartik K. Agaram2015-07-103-38/+23
| | | | | | | 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.
* 1750Kartik K. Agaram2015-07-101-0/+1
| | | | | 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.
* 1749 - investigating yesterday's sluggishnessKartik K. Agaram2015-07-101-2/+21
| | | | | | 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.
* 1748Kartik K. Agaram2015-07-101-3/+3
|
* 1747Kartik K. Agaram2015-07-101-4/+3
|
* 1746 - load file and run a single testKartik K. Agaram2015-07-102-8/+7
| | | | $ ./mu test run-instruction-and-print-warnings
* 1745 - hoist warning/response strings out of editor-dataKartik K. Agaram2015-07-103-278/+326
| | | | | | | | | | 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.
* 1744 - support just two editors rather than a listKartik K. Agaram2015-07-094-245/+171
| | | | | Current model: you click on something to put it on the editor at the top of the column. Worth a shot.
* 1743Kartik K. Agaram2015-07-092-178/+186
|
* 1742Kartik K. Agaram2015-07-091-23/+19
|
* 1741 - start cleaning up editor-dataKartik K. Agaram2015-07-091-19/+14
|
* 1740 - correct redraw after reducing editor sizeKartik K. Agaram2015-07-091-20/+17
| | | | | 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.
* 1739Kartik K. Agaram2015-07-091-1/+0
| | | | Leaves a line blank after printing result/warnings, for some reason.
* 1738Kartik K. Agaram2015-07-091-9/+1
|
* 1737 - allow editors to 'grow'Kartik K. Agaram2015-07-091-16/+24
|
* 1736 - stop refusing to reload code in the editorKartik K. Agaram2015-07-092-1/+7
| | | | All tests passing, but early layers are broken.
* 1735Kartik K. Agaram2015-07-081-0/+1
| | | | | | 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.
* 1734Kartik K. Agaram2015-07-081-42/+20
| | | | Pushing back some of the weight of repetitive boilerplate.
* 1733 - load all recipes before running sandboxesKartik K. Agaram2015-07-082-37/+172
| | | | | This is starting to look good! I need to add some tests for render-string, but we'll see.
* 1732Kartik K. Agaram2015-07-081-12/+0
|
* 1731 - ah, now fully responsiveKartik K. Agaram2015-07-085-1/+36
| | | | The trick is to check for more events and not bother rendering if so.
* 1730Kartik K. Agaram2015-07-081-5/+5
| | | | Switch to F10 because F9 is in use under my setup.
* 1729Kartik K. Agaram2015-07-081-25/+0
|
* 1728Kartik K. Agaram2015-07-081-1/+7
|
* 1727Kartik K. Agaram2015-07-081-2/+34
|
* 1726Kartik K. Agaram2015-07-082-13/+52
|
* 1725Kartik K. Agaram2015-07-081-1/+5
|
* 1724 - first stab at printing interactive resultsKartik K. Agaram2015-07-083-3/+48
|
* 1723Kartik K. Agaram2015-07-083-12/+13
| | | | | Some reorg before we start plumbing 'reply' from 'run-interactive' to return a string containing the results.
* 1722 - drop support for querying locationsKartik K. Agaram2015-07-082-76/+23
| | | | | | | | | | | | 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.
* 1721 - hide warnings inside interactive routinesKartik K. Agaram2015-07-086-18/+107
| | | | | | | | | | 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.
* 1720 - start adding repl supportKartik K. Agaram2015-07-072-8/+110
|
* 1719 - start using configurable event-handlerKartik K. Agaram2015-07-071-5/+7
|
* 1718 - delete repl.muKartik K. Agaram2015-07-071-840/+0
| | | | | | 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.
* 1717 - less hacky replKartik K. Agaram2015-07-072-58/+81
| | | | | | | '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.
* 1716Kartik K. Agaram2015-07-072-5/+12
|
* 1715 - slightly more responsiveKartik K. Agaram2015-07-061-16/+10
| | | | | | | | | 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.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-15 23:40:17 +0000