about summary refs log tree commit diff stats
path: root/edit/005-sandbox.mu
Commit message (Collapse)AuthorAgeFilesLines
* 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
|
* 2595 - bugfix: update state when restoring sandboxesKartik K. Agaram2016-01-231-0/+3
|
* 2594 - bugfixes: managing state when deletingKartik K. Agaram2016-01-231-84/+90
| | | | This required completely redesigning scrolling.
* 2592 - bugfix: sandbox title bar managementKartik K. Agaram2016-01-221-1/+85
|
* 2590 - support scrolling through sandboxesKartik K. Agaram2016-01-221-2/+371
|
* 2589 - tweak color for sandbox labelsKartik K. Agaram2016-01-221-2/+2
| | | | | | | | | | | | | | | | | | | | I'm now thinking about how to support scrolling on the sandbox side. Caleb's idea is to use down-arrow inside the sandbox editor, and then "scroll off" the editor to the top of each successive sandbox. I think I'll reserve the white background as the cursor color in that situation. I wonder if I should just undo all the support for sandbox labels since yesterday. Labels are perhaps superfluous once I support scrolling and reorder sandboxes to always throw ones with errors up top. But then you can end up scrolling through lots of tests without any sense of how far down you are. So the other approach is to keep labels and try to keep them stable, not reorder them. Looking further ahead I'm going to need a way to jump to a specific sandbox. Maybe instead of reordering sandboxes I should just automatically render from the first sandbox with error. Maybe show the number of failed sandboxes in the status instead of the index of the first failure.
* 2586 - show first sandbox with error in statusKartik K. Agaram2016-01-221-5/+10
|
* 2585 - label sandboxes with a numberKartik K. Agaram2016-01-221-9/+18
| | | | | | | | | It also seems useful that the number maps to the name of the file the sandbox is saved in. However this mapping is currently a happy accident and not actually tested. I'm starting to switch gears and help make the editor useable with many many sandboxes. This is just the first step of several.
* 2576 - distinguish allocated addresses from othersKartik K. Agaram2016-01-191-76/+76
| | | | | | | | | | | | | | | | This is the one major refinement on the C programming model I'm planning to introduce in mu. Instead of Rust's menagerie of pointer types and static checking, I want to introduce just one new type, and use it to perform ref-counting at runtime. So far all we're doing is updating new's interface. The actual ref-counting implementation is next. One implication: I might sometimes need duplicate implementations for a recipe with allocated vs vanilla addresses of the same type. So far it seems I can get away with just always passing in allocated addresses; the situations when you want to pass an unallocated address to a recipe should be few and far between.
* 2548 - teach 'print' to print integersKartik K. Agaram2015-12-281-6/+9
| | | | | | | | | | Still can't print non-integer numbers, so this is a bit hacky. The big consequence is that you can't print literal characters anymore because of our rules about how we pick which variant to statically dispatch to. You have to save to a character variable first. Maybe I can add an annotation to literals..
* three bugs fixedKartik K. Agaram2015-12-151-0/+3
| | | | | | | | | | | | | | | | | - notes bug in edit/ triggers in immutable but not master branch bug triggered by changes to layer 059: we're finding an unspecialized call to 'length' in 'append_6' hard to debug because trace isn't complete just bring out the big hammer: use a new log file length_2 from recipes.mu is not being deleted (bug #1) so reload doesn't switch length to length_2 when variant_already_exists (bug #2) so we end up saving in Recipe for a primitive ordinal so no valid specialization is found for 'length' (bug #3) why doesn't it trigger in a non-interactive scenario? argh, wasn't checking for an empty line at end. ok, confidence restored.
* rest of edit/ fixedKartik K. Agaram2015-12-151-1/+1
| | | | No more bugs; phew.
* 2477Kartik K. Agaram2015-11-271-2/+2
|
* 2476Kartik K. Agaram2015-11-271-1/+1
|
* 2468 - overload print-character as just 'print'Kartik K. Agaram2015-11-211-7/+7
|
* 2467 - rename 'string' to 'text' everywhereKartik K. Agaram2015-11-211-8/+8
| | | | | | | | Not entirely happy with this. Maybe we'll find a better name. But at least it's an improvement. One part I *am* happy with is renaming string-replace to replace, string-append to append, etc. Overdue, now that we have static dispatch.
* 2466 - eliminate ':string' from scenariosKartik K. Agaram2015-11-211-1/+1
|
* 2446 - drop '-duplex' namespacing in recipesKartik K. Agaram2015-11-151-3/+3
| | | | Great that it just worked after the previous commit.
* 2442Kartik K. Agaram2015-11-151-2/+1
| | | | | | Fix the drawback in the previous commit: if an ingredient is just a literal 0 we'll skip its type-checking and hope to map type ingredients elsewhere.
* 2441 - never miss any specializationsKartik K. Agaram2015-11-151-1/+2
| | | | | | | | | I was failing to specialize calls containing literals. And then I had to deal with whether literals should map to numbers or characters. (Answer: both.) One of the issues that still remains: shape-shifting recipes can't be called with literals for addresses, even if it's 0.