about summary refs log tree commit diff stats
path: root/sandbox/007-sandbox-delete.mu
Commit message (Collapse)AuthorAgeFilesLines
* 2735 - define recipes using 'def'Kartik K. Agaram2016-03-081-4/+4
| | | | | | | | | | | | 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.
* 2608 - fix-up tests in sandbox/ appKartik K. Agaram2016-01-271-12/+4
| | | | | | | | | | 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.
* 2594 - bugfixes: managing state when deletingKartik K. Agaram2016-01-231-2/+213
| | | | This required completely redesigning scrolling.
* 2590 - support scrolling through sandboxesKartik K. Agaram2016-01-221-1/+1
|
* 2585 - label sandboxes with a numberKartik K. Agaram2016-01-221-3/+3
| | | | | | | | | 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-9/+9
| | | | | | | | | | | | | | | | 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.
* support immutability checks in sandbox/ appKartik K. Agaram2015-12-151-1/+1
|
* 2428 - sandbox/ working againKartik K. Agaram2015-11-121-4/+2
|
* 2309Kartik K. Agaram2015-10-281-4/+4
|
* 2260 - start tracing by depth rather than labelKartik K. Agaram2015-10-061-1/+1
| | | | Now we can collect all traces, just modulating the depth.
* 2183 - environment + external editor using tmuxKartik K. Agaram2015-09-121-0/+108
Thanks Jack and Caleb Couch for the idea.