akkartik/mu
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
2894e8d5de
mu/sandbox/007-sandbox-delete.mu

107 lines
4.5 KiB
Plaintext
Raw Normal View History

2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
## deleting sandboxes
scenario deleting-sandboxes [
2260 - start tracing by depth rather than label Now we can collect all traces, just modulating the depth.
2015-10-07 06:38:28 +00:00
trace-until 100/app # trace too long
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
assume-screen 50/width, 15/height
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
1:address:shared:array:character <- new []
2:address:shared:programming-environment-data <- new-programming-environment screen:address:shared:screen, 1:address:shared:array:character
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
# run a few commands
assume-console [
left-click 1, 0
type [divide-with-remainder 11, 3]
press F4
type [add 2, 2]
press F4
]
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
event-loop screen:address:shared:screen, console:address:shared:console, 2:address:shared:programming-environment-data
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
screen-should-contain [
. run (F4) .
. .
.━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━.
2585 - label sandboxes with a number 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.
2016-01-21 21:51:50 +00:00
.0 x.
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
.add 2, 2 .
.4 .
.━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━.
2585 - label sandboxes with a number 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.
2016-01-21 21:51:50 +00:00
.1 x.
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
.divide-with-remainder 11, 3 .
.3 .
.2 .
.━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━.
. .
]
# delete second sandbox
assume-console [
left-click 7, 49
]
run [
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
event-loop screen:address:shared:screen, console:address:shared:console, 2:address:shared:programming-environment-data
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
]
screen-should-contain [
. run (F4) .
. .
.━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━.
2585 - label sandboxes with a number 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.
2016-01-21 21:51:50 +00:00
.0 x.
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
.add 2, 2 .
.4 .
.━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━.
. .
. .
]
# delete first sandbox
assume-console [
left-click 3, 49
]
run [
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
event-loop screen:address:shared:screen, console:address:shared:console, 2:address:shared:programming-environment-data
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
]
screen-should-contain [
. run (F4) .
. .
.━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━.
. .
. .
]
]
after <global-touch> [
# on a sandbox delete icon? process delete
{
was-delete?:boolean <- delete-sandbox *t, env
break-unless was-delete?
hide-screen screen
screen <- render-sandbox-side screen, env
screen <- update-cursor screen, current-sandbox
show-screen screen
loop +next-event:label
}
]
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
recipe delete-sandbox t:touch-event, env:address:shared:programming-environment-data -> was-delete?:boolean, env:address:shared:programming-environment-data [
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
local-scope
2428 - sandbox/ working again
2015-11-13 06:31:49 +00:00
load-ingredients
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
click-column:number <- get t, column:offset
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
current-sandbox:address:shared:editor-data <- get *env, current-sandbox:offset
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
right:number <- get *current-sandbox, right:offset
at-right?:boolean <- equal click-column, right
reply-unless at-right?, 0/false
click-row:number <- get t, row:offset
2576 - distinguish allocated addresses from others 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.
2016-01-20 07:18:03 +00:00
prev:address:address:shared:sandbox-data <- get-address *env, sandbox:offset
curr:address:shared:sandbox-data <- get *env, sandbox:offset
2183 - environment + external editor using tmux Thanks Jack and Caleb Couch for the idea.
2015-09-12 20:49:50 +00:00
{
break-unless curr
# more sandboxes to check
{
target-row:number <- get *curr, starting-row-on-screen:offset
delete-curr?:boolean <- equal target-row, click-row
break-unless delete-curr?
# delete this sandbox, rerender and stop
*prev <- get *curr, next-sandbox:offset
reply 1/true
}
prev <- get-address *curr, next-sandbox:offset
curr <- get *curr, next-sandbox:offset
loop
}
reply 0/false
]
Reference in New Issue Copy Permalink