about summary refs log tree commit diff stats
Commit message (Collapse)AuthorAgeFilesLines
* maintain aspect ratio when rendering imagesKartik K. Agaram2021-07-293-8/+43
|
* .Kartik K. Agaram2021-07-291-0/+2
|
* downsampling photos makes the dithering seem worseKartik K. Agaram2021-07-291-2/+2
| | | | We support 128px, so let's use the whole 128px.
* .Kartik K. Agaram2021-07-291-1/+1
|
* shell: reliable image renderingKartik K. Agaram2021-07-291-0/+1
|
* shell: rendering image definitionsKartik K. Agaram2021-07-291-1/+68
| | | | | | Not quite working yet. Only the very first rendering succeeds. After that any keypress triggers a second render which aborts. Image is getting corrupted in memory somehow.
* shell: support loading 128x128px imagesKartik K. Agaram2021-07-286-10/+10
| | | | | | I'm loading them in uncompressed ASCII format, and all streams and gap buffers all over the place need to get massively scaled up to 256KB capacity. But the tests don't yet run out of RAM, so I'll keep going.
* shell: literal imagesKartik K. Agaram2021-07-286-8/+42
|
* saving definitions containing string literalsKartik K. Agaram2021-07-281-2/+0
| | | | | | | This was the whole proximal goal in implementing balanced terminals. Printing these is still unreliable. It always surrounds in [], which may not work.
* .Kartik K. Agaram2021-07-282-22/+0
|
* .Kartik K. Agaram2021-07-281-0/+142
|
* shell: second notation for string literalsKartik K. Agaram2021-07-281-5/+126
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | I've always been dissatisfied with the notion of escaping. It introduces a special-case meta-notation within the tokenizer, and the conventional approach leads to exponential "leaning toothpick syndrome" with each level of escaping. One potential "correct" solution is to keep string terminals parameterizable: [abc] => abc [=] => = [=[abc]=] => abc [=[a]bc]=] => a]bc [==[a]=]bc]==] => a]=]bc ..and so on. Basically the terminals grow linearly as the number of escapings grow. While this is workable, I'd like to wait until I actually need it, and then gauge whether the need is a sign of the stack growing too complex, with too many layers of notation/parsing. Mu's goal is just 3 notations, and it's going to require constant vigilance to keep that from growing. Therefore, for now, there are two notations for string literals, one symmetric and one balanced: "abc" => abc [abc] => abc The balancing notation permits nested brackets as long as they balance. [abc [def]] => abc [def] If you need unbalanced square brackets, use the symmetric terminals: "abc [def" => abc [def If you need double quotes inside strings, use the balanced notation: [abc "def] => abc "def If you need _both_ square brackets (whether balanced or unbalanced) and double quotes, you're currently shit outta luck.
* shell: render image from pbm data streamKartik K. Agaram2021-07-275-5/+239
|
* .Kartik K. Agaram2021-07-261-0/+74
|
* .Kartik K. Agaram2021-07-261-0/+2
|
* .Kartik K. Agaram2021-07-262-4/+16
|
* .Kartik K. Agaram2021-07-261-1/+1
|
* game of life in lispKartik K. Agaram2021-07-263-47/+109
| | | | | | | | Super slow; each frame is cleared as a sort of progress indicator while it computes the next frame. In the process I realize I need to adjust every single trace in the shell sources to be more fault-tolerant to a filled-up trace stream.
* .Kartik K. Agaram2021-07-263-10/+40
| | | | | Smoked out some issues by rendering a single frame of Game of Life. Incredibly slow.
* gracefully trace large multi-dimensional arraysKartik K. Agaram2021-07-261-4/+10
|
* gracefully trace large arraysKartik K. Agaram2021-07-261-0/+8
|
* palette operations now a bit fasterKartik K. Agaram2021-07-261-7/+9
|
* .Kartik K. Agaram2021-07-261-0/+6
|
* .Kartik K. Agaram2021-07-261-3/+3
|
* shell primitive: initialize array of some sizeKartik K. Agaram2021-07-261-0/+78
|
* shell primitive: iset to mutate array at indexKartik K. Agaram2021-07-251-1/+104
|
* shell primitive: array indexKartik K. Agaram2021-07-251-1/+82
|
* shell: array typeKartik K. Agaram2021-07-254-1/+161
|
* .Kartik K. Agaram2021-07-251-9/+9
|
* .Kartik K. Agaram2021-07-251-5/+5
|
* .Kartik K. Agaram2021-07-251-4/+4
|
* shell: starting to implement arraysKartik K. Agaram2021-07-252-5/+65
|
* .Kartik K. Agaram2021-07-251-11/+10
|
* .Kartik K. Agaram2021-07-241-0/+3
|
* .Kartik K. Agaram2021-07-241-5/+4
|
* .Kartik K. Agaram2021-07-222-31/+0
|
* update memory map doc and anticipate a gotchaKartik K. Agaram2021-07-223-3/+15
|
* .Kartik K. Agaram2021-07-203-46/+46
|
* .Kartik K. Agaram2021-07-2039-531/+94
|
* .Kartik K. Agaram2021-07-2018-41/+41
| | | | | Update run instructions for linux/app/ examples, and make sure they are correct.
* .Kartik K. Agaram2021-07-204-1346/+2
| | | | | Delete the examples from Crenshaw. They're extremely rudimentary, and they were really just trial runs for the Mu toolchain.
* start work on running the Mu toolchain atop MuKartik K. Agaram2021-07-1914-14/+14
|
* .Kartik K. Agaram2021-07-192-10/+3
|
* .Kartik K. Agaram2021-07-192-3/+71
|
* 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-192-2/+1
|
* .Kartik K. Agaram2021-07-191-176/+0
|
* render functions in MRU orderKartik K. Agaram2021-07-194-45/+92
|
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-23 00:36:37 +0000