about summary refs log tree commit diff stats
path: root/edit/005-sandbox.mu
Commit message (Collapse)AuthorAgeFilesLines
* 3796Kartik K. Agaram2017-03-141-26/+45
| | | | | | Standardize the order of some common blocks in `render`, `render-text` and `render-code`. This is preparation for trying to reorganize them to reduce duplicate code.
* 3794Kartik K. Agaram2017-03-141-2/+2
| | | | Fix a _very_ misleading comment.
* 3793Kartik K. Agaram2017-03-141-0/+63
| | | | | | Move 'render-code' to the layer where it's used. Thanks Caleb Couch for finding this bit of ugliness.
* 3790Kartik K. Agaram2017-03-121-1/+4
| | | | Don't try to snapshot in scenarios.
* 3789Kartik K. Agaram2017-03-121-1/+3
| | | | | | | | | | | | | I accidentally got rid of git snapshotting of lessons back when I switched to testable file primitives last December (commit 3705). >:-( Bringing it back now, hopefully better. The improvement is that there's now at most one commit every time we hit F4. This change adds yet another reason that running `mu` from a different directory is just not supported.
* 3748Kartik K. Agaram2017-02-281-1/+1
|
* 3745Kartik K. Agaram2017-02-071-0/+1213
| | | | | | | Stop trying to create a new layer showing how we minimize prints. Stephen's suggestion is to create a data structure that encapsulates instructions to `insert-at-cursor` for either just printing a character to screen or rendering everything. Let's try that at some point.
* 3738 - start on new edit/ layer: minimizing printsKartik K. Agaram2017-02-041-1213/+0
|
* 3735 - get rid of 'print-integer'Kartik K. Agaram2017-01-221-2/+2
| | | | | We do support printing non-integer numbers for some time, albeit using the underlying host platform.
* 3705 - switch to tested file-system primitivesKartik K. Agaram2016-12-111-73/+97
|
* 3696Kartik K. Agaram2016-11-271-1/+1
| | | | | | Decouple editor initialization from rendering to screen. This hugely simplifies the header of 'new-editor' and makes clear that it was only using the screen for rendering.
* 3687Kartik K. Agaram2016-11-251-1/+1
|
* 3686Kartik K. Agaram2016-11-251-4/+4
|
* 3561Kartik K. Agaram2016-10-221-1/+1
|
* 3552Kartik K. Agaram2016-10-221-9/+9
| | | | | | | | | | | | | | | | | | Stop requiring jump instructions to explicitly provide a ':label' type for jump targets. This has been a source of repeated confusion for my students: a) They'd add the ':label' to the label definition rather than the jump target (label use) b) They'd spend time thinking about whether the initial '+' prefix was part of the label name. In the process I cleaned up a couple of things: - the space of names is more cleanly partitioned into labels and non-labels (clarifying that '_' and '-' are non-label prefixes) - you can't use label names as regular variables anymore - you can infer the type of a label just from its name
* 3490Kartik K. Agaram2016-10-091-45/+45
| | | | | | | | | | | | | | | Redo commit 3457. Basically there were 3 unicode characters we changed back then: solid horizontal line: 9473 -> 9472 fuzzy horizontal line: 9480 -> 9548 fuzzy vertical line: 9482 -> 9550 The solid horizontal line has no issues, so we just redo it here. For the other two, we'll perform the substitution only when rendering html. That gives us the best of both worlds: the scenario screens render right in html, and alt-tabbing continues to be snappy when running the edit/ app.
* 3489Kartik K. Agaram2016-10-081-171/+171
| | | | | | | | | | Revert commit 3457, where I switched the unicode characters used in the edit/ app to something that doesn't render double-wide in html. It turns out that the new unicode characters made iTerm2 sluggish in alt-tabbing between windows. (Commit 3488 only fixed the screen-clearing issue.) I haven't reverted the html files. I'm going to redo commit 3457 next so the html files continue to render like they do now.
* 3457Kartik K. Agaram2016-10-061-171/+171
| | | | | Switch around some unicode characters in the edit/ app so that it renders more cleanly in html (with monospace fonts).
* 3445Kartik K. Agaram2016-10-061-47/+47
| | | | | | | Ugly that we didn't need 'screen' to provide a type in scenarios (because assume-screen expands to a definition of 'screen') but we did need a type for 'console'. Just never require types for special names in scenarios.
* 3429 - standardize Mu scenariosKartik K. Agaram2016-09-281-67/+62
| | | | | | | | | | | | | A long-standing problem has been that I couldn't spread code across 'run' blocks because they were separate scopes, so I've ended up making them effectively comments. Running code inside a 'run' block is identical in every way to simply running the code directly. The 'run' block is merely a visual aid to separate setup from the component under test. In the process I've also standardized all Mu scenarios to always run in a local scope, and only use (raw) numeric addresses for values they want to check later.
* 3396Kartik K. Agaram2016-09-171-73/+73
|
* 3391 - type abbreviations everywhereKartik K. Agaram2016-09-171-197/+197
| | | | | | | | | Well, almost. I can't use them in some places in C++ where I'm just creating a temporary reagent without passing it through transforms. Like in some unit tests. I can't use them in memory-should-contain. And there's one remaining bug: I can't use abbreviations in a couple of places in 075channel.mu.
* 3341Kartik K. Agaram2016-09-121-3/+3
| | | | | | | Process type abbreviations in function headers. Still a couple of places where doing this causes strange errors. We'll track those down next.
* 3338Kartik K. Agaram2016-09-121-2/+2
| | | | Process type abbreviations in container definitions.
* 3337 - first use of type abbreviations: textKartik K. Agaram2016-09-121-37/+37
| | | | | In the process I've uncover a couple of situations we don't support type abbreviations yet. They're next.
* 3168 - skip loading recipe 'main' in edit/Kartik K. Agaram2016-08-121-1/+1
| | | | | | | This is part of efforts to allow students to transition gradually from the sandbox to running programs directly on the commandline, writing real scenarios, etc. Running on the commandline requires 'main', but overriding 'main' would mess up edit/ which is itself a Mu program.
* 3067Kartik K. Agaram2016-06-251-2/+64
|
* 3052 - make edit/ render functions higher-orderKartik K. Agaram2016-06-121-14/+14
| | | | | | This required the fix of 3051 to first-class recipe support, and will next enable us to keep the cursor from moving in response to resize events.
* 3025 - fix a minor annoyance in edit/Kartik K. Agaram2016-05-291-3/+157
| | | | | When I floor the down-arrow too much, don't scroll unnecessarily off the bottom of the screen. But *do* scroll if there's errors to show.
* 2983 - migrate buttons over to sandbox/Kartik K. Agaram2016-05-191-7/+0
|
* 2982Kartik K. Agaram2016-05-191-6/+6
|
* 2980Kartik K. Agaram2016-05-191-0/+3
|
* 2977 - draw new sandbox menu in edit/Kartik K. Agaram2016-05-191-139/+160
| | | | | | | | | | | | | Doesn't work as advertised yet. This is just the render piece, and fixing all the tests. I've been careful to try to break tests for edit once I implement the button. Delete I can't ensure will break afterwards. Remember to test clicking on multiple places on the menu. Managing the screens is starting to grow onerous; maybe we need something called normalize which clears some things. But the sandbox menu can be on arbitrary lines..
* 2976Kartik K. Agaram2016-05-191-4/+18
|
* 2975Kartik K. Agaram2016-05-191-1/+1
| | | | Clean up this helper before we start redoing sandbox menubars.
* 2954 - bugfix: $systemKartik K. Agaram2016-05-111-8/+1
| | | | The actual fix is in the layer rewriting literal strings.
* 2953 - use pgup/pgdn to scroll through sandboxesKartik K. Agaram2016-05-111-48/+37
| | | | | | In the process I've also simplified the sandbox/ app. Since it's impossible for sandbox editors to span multiple pages, we can drop all scroll support altogether.
* 2928 - fix sandbox restore in edit/ and sandbox/Kartik K. Agaram2016-05-051-3/+7
| | | | | This had been broken ever since 2854, because we can't write tests for restore-snapshots at the moment.
* 2864 - replace all address:shared with just addressKartik K. Agaram2016-04-241-107/+107
| | | | | | | Now that we no longer have non-shared addresses, we can just always track refcounts for all addresses. Phew!
* 2861 - 'maybe-convert' no longer returns addressKartik K. Agaram2016-04-231-3/+3
|
* 2853 - purge get-address from edit/ appKartik K. Agaram2016-04-221-41/+40
| | | | Phew!
* 2782 - directly use string literals everywhereKartik K. Agaram2016-03-141-9/+4
|
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-22/+22
| | | | | | | | | | | | I'm dropping all mention of 'recipe' terminology from the Readme. That way I hope to avoid further bike-shedding discussions while I very slowly decide on the right terminology with my students. I could be smarter in my error messages and use 'recipe' when code uses it and 'function' otherwise. But what about other words like ingredient? It would all add complexity that I'm not yet sure is worthwhile. But I do want separate experiences for veteran programmers reading about Mu on github and for people learning programming using Mu.
* 2716 - more holes in immutability checksKartik K. Agaram2016-02-261-1/+1
| | | | | We're still not done. Layer 60 doesn't yet handle variables in surrounding spaces. There's probably other issues..
* 2707Kartik K. Agaram2016-02-251-5/+0
|
* 2624Kartik K. Agaram2016-02-011-9/+2
| | | | Reorganize further to make edit/008-sandbox-test more self-contained.
* 2623 - bugfix: editing sandboxesKartik K. Agaram2016-02-011-5/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | If you restore 2 sandboxes, the first render was setting response-starting-row-on-screen on both, without ever rendering a response. If the lower sandbox contained a print and rendered the screen instead of the response, the original response-starting-row-on-screen was never reset. If the process of running the sandboxes caused the lower sandbox's title bar to move below the now-stale response-starting-row-on-screen[1], editing the lower sandbox no longer works. [1] (Either because the upper sandbox prints to screen as well (causing the first F4 to move the lower sandbox down by several lines), or because a fresh sandbox is created with several lines before the first F4 is hit.) Current solution: never set response-starting-row-on-screen during reload (or otherwise when there's no response). This is hard to test right now because 'restore' is not a tested interface, and I can't come up with another situation where the response-starting-row-on-screen goes stale. So I'm now trying to keep all changes to response-starting-row-on-screen close together. Another idea is to add a check that the click row lies below the response-starting row *and* above the start of the next sandbox. (But what if there's no next sandbox?) (This bug is really a regression, introduced last Sep in 2163.)
* 2610 - warn when recipes don't use default-spaceKartik K. Agaram2016-01-271-9/+12
| | | | Somehow this never transferred over from the Arc version until now.
* 2608 - fix-up tests in sandbox/ appKartik K. Agaram2016-01-271-13/+6
| | | | | | | | | | When I first forked it from the edit/ app, I wasn't sure how to deal with changing the recipe side when the only way the program accesses it is with the untestable 'restore' hack. Now we introduce a little hook into event-loop and pass in any updated recipe side directly. In the process I've cleaned up several minor stylistic inconsistencies between edit/ and sandbox/ apps.
* 2602Kartik K. Agaram2016-01-241-1/+1
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-12-02 23:37:39 +0000