about summary refs log tree commit diff stats
path: root/shell
Commit message (Collapse)AuthorAgeFilesLines
* error message when trying to jump to primitiveKartik K. Agaram2021-07-191-0/+15
|
* .Kartik K. Agaram2021-07-191-9/+9
|
* .Kartik K. Agaram2021-07-191-21/+0
|
* .Kartik K. Agaram2021-07-191-1/+1
|
* render functions in MRU orderKartik K. Agaram2021-07-192-45/+70
|
* .Kartik K. Agaram2021-07-171-2/+2
|
* .Kartik K. Agaram2021-07-161-1/+1
|
* .Kartik K. Agaram2021-07-081-4/+4
|
* primitives for double-bufferingKartik K. Agaram2021-07-051-4/+152
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I thought I needed these for this bouncing-ball demo: def (bounce screen) with (w (width screen) h (height screen) cx 16 cy 16 dx 12 dy 19) while 1 clear screen ring screen cx cy 16 3 5 cx += dx cy += dy when (or (cx > w) (cx < 0)) set dx 0-dx when (or (cy > h) (cy < 0)) set dy 0-dy for _ 0 (< _ 100) ++_ # delay No matter how I adjusted the delay I couldn't get rid of the jitter. So I built a double-buffered version: (bounce2 . [def (bounce2 screen) with (w (width screen) h (height screen) cx 16 cy 16 dx 12 dy 19 screen2 (new_screen (columns screen) (lines screen))) while 1 clear screen2 ring screen2 cx cy 16 3 5 cx += dx cy += dy when (or (cx > w) (cx < 0)) set dx 0-dx when (or (cy > h) (cy < 0)) set dy 0-dy blit screen2 screen for _ 0 (< _ 100) ++_]) # delay But it didn't make a difference! Turns out nothing will help you when successive frames are too far apart. This is the correct tweak to `bounce`: - dx 12 - dy 19) + dx 1 + dy (/ 19 12)) Still, we'll keep double-buffering around for the future.
* shell: fix clear on screensKartik K. Agaram2021-07-051-1/+1
| | | | | | | Broken since commit c95648c96 on Jul 3. Unclear what test to write for this. Should clear-stream check for NULL? Should apply-clear?
* expose Mu implementation of 'bezier'Kartik K. Agaram2021-07-051-1/+256
| | | | Still no support for acute-angled control points.
* replace 'circle' with Mu implementationKartik K. Agaram2021-07-052-19/+161
|
* replace 'vline' with Mu implementationKartik K. Agaram2021-07-052-6/+162
|
* replace 'hline' with Mu implementationKartik K. Agaram2021-07-052-9/+165
|
* replace 'line' with Mu implementationKartik K. Agaram2021-07-052-32/+196
|
* .Kartik K. Agaram2021-07-051-1/+1
|
* .Kartik K. Agaram2021-07-051-140/+140
|
* reading from streamsKartik K. Agaram2021-07-034-22/+152
| | | | | | The Mu shell has no string literals, only streams. No random access, only sequential access. But I've been playing fast and loose with its read pointer until now. Hopefully things are cleaned up now.
* alistsKartik K. Agaram2021-07-031-0/+13
|
* new primitive: cons?Kartik K. Agaram2021-07-031-1/+42
|
* .Kartik K. Agaram2021-07-031-5/+10
|
* .Kartik K. Agaram2021-07-031-4/+4
|
* reorg primitives on screenKartik K. Agaram2021-07-022-43/+80
|
* clean up final abort in macroexpandKartik K. Agaram2021-06-302-1/+14
|
* delete a known issueKartik Agaram2021-06-301-3/+0
| | | | I can't reproduce the issue with the keyboard handler anymore :/
* .Kartik K. Agaram2021-06-271-5/+11
|
* simplify Qemu instructionsKartik K. Agaram2021-06-271-12/+10
| | | | | Turns out we don't need a special case for KVM. https://qemu.readthedocs.io/en/latest/system/invocation.html
* .Kartik Agaram2021-06-241-3/+3
|
* .Kartik Agaram2021-06-241-1/+1
|
* .Kartik Agaram2021-06-241-1/+1
|
* .Kartik Agaram2021-06-231-1/+1
|
* .Kartik Agaram2021-06-231-8/+0
|
* .Kartik Agaram2021-06-231-1/+1
|
* .Kartik Agaram2021-06-231-2/+2
|
* .Kartik Agaram2021-06-231-4/+4
|
* .Kartik Agaram2021-06-231-1/+1
|
* one more bug, and documentation for infixKartik K. Agaram2021-06-234-27/+80
| | | | One error message gets a bit worse.
* .Kartik K. Agaram2021-06-231-3/+3
|
* .Kartik K. Agaram2021-06-231-8/+8
|
* one more bugKartik K. Agaram2021-06-232-9/+22
|
* start using infix in data diskKartik K. Agaram2021-06-231-57/+54
| | | | Still some gaps to track down.
* all tests passing again; infix seems doneKartik K. Agaram2021-06-222-1/+7
|
* infix tests passing but something's still brokenKartik K. Agaram2021-06-221-2/+48
|
* 2 failing tests remainingKartik K. Agaram2021-06-221-2/+44
| | | | We just need to support unary operators.
* almost there; this is encouragingKartik K. Agaram2021-06-221-16/+21
| | | | The at-head-of-list? is a really ugly hack, though.
* beginnings of tokenization within symbolsKartik K. Agaram2021-06-222-17/+68
| | | | We're now down to 4 failing tests. But these will require surgery.
* .Kartik K. Agaram2021-06-221-11/+3
|
* clean up lexical categoriesKartik K. Agaram2021-06-222-142/+48
|
* snapshotKartik K. Agaram2021-06-221-3/+32
| | | | | Still a couple of failing tests before I switch gears to breaking down symbols containing infix.
* .Kartik K. Agaram2021-06-221-3/+5
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-26 15:00:14 +0000