about summary refs log tree commit diff stats
path: root/baremetal
Commit message (Collapse)AuthorAgeFilesLines
* 7550Kartik Agaram2021-01-231-3/+2
|
* 7548 - baremetal: better cursor managementKartik Agaram2021-01-236-44/+73
|
* 7547 - baremetal: rpn calculatorKartik Agaram2021-01-229-6/+4217
| | | | | | | | Still in progress. Known bugs: * Cursor management is broken. Every line currently seems to leave behind a shadow cursor. * No shift-key support yet, which means no addition or multiplication. (This app doesn't have division yet.)
* 7545Kartik Agaram2021-01-221-28/+32
|
* 7543Kartik Agaram2021-01-221-11/+11
|
* 7542 - baremetal: support cursor on a graphemeKartik Agaram2021-01-224-18/+36
| | | | | | | | | | | | | | | So far we've drawn a space implicitly at the cursor. Now I allow drawing an arbitrary grapheme when drawing the cursor. But the caller has to specify what to draw. (The alternative would be for layer 103 to track every single grapheme on screen along with its color and any other future attributes, just to be able to paint and unpaint the background for a single character.) I've modified existing helpers for drawing multiple graphemes to always clear the final cursor position after they finish drawing. That seems reasonable for terminal-like applications. Applications that need to control the screen in a more random-access manner will need to track the grapheme at the cursor for themselves.
* 7541 - baremetal: debug screen test helpersKartik Agaram2021-01-221-7/+25
|
* 7540 - baremetal: cursorKartik Agaram2021-01-222-9/+19
| | | | | | | | | | | | | | | | | | | | I spent over a week agonizing over this. * I had to come to terms with the fact that I don't really know how to make pixel graphics testable. ASCII art on a pixel by pixel basis feels inhuman. Just focus on text mode for now. * I had to set aside the problem of non-English family languages. Languages like Arabic that can stack complex graphemes together likely can't be fixed-width. But I don't know enough at the moment to solve for them. * I spent a while trying to juggle two cursors, one invisible output cursor for tracking the most recent print, and one visible one that's just a hint to the user of what the next keystroke will do. But it looks like I can fold both into a single cursor. Drawing things updates the location of the cursor but doesn't display it. Explicitly moving the cursor displays it, but future drawing can overwrite the cursor.
* 7539 - baremetal: handle unrecognized keysKartik Agaram2021-01-221-7/+11
|
* 7538 - baremetal: screen coords in graphemesKartik Agaram2021-01-224-42/+54
|
* 7537 - baremetal: start of cursor supportKartik Agaram2021-01-193-7/+10
|
* 7536Kartik Agaram2021-01-191-7/+7
|
* 7535Kartik Agaram2021-01-176-14/+14
|
* 7534Kartik Agaram2021-01-172-25/+47
| | | | Don't assume screen dimensions.
* 7533Kartik Agaram2021-01-163-0/+23
| | | | Both issues of commit 7531 fixed.
* 7532Kartik Agaram2021-01-161-2/+2
|
* 7531 - checking fake screensKartik Agaram2021-01-161-0/+145
| | | | | | This uncovers two open issues: * incrementing the cursor after drawing a single grapheme * needing to clear background pixels when drawing a grapheme
* 7530 - baremetal: print ints to screenKartik Agaram2021-01-166-2/+807
|
* 7529 - baremetal: fake screenKartik Agaram2021-01-163-7/+214
|
* 7528 - heap allocatorKartik Agaram2021-01-164-4/+843
|
* 7527Kartik Agaram2021-01-162-0/+3
|
* 7525Kartik Agaram2021-01-161-1/+35
| | | | | | Bring back runtime support for bounds-checking arrays. Again, the error messages kinda suck, because I can't yet print integers. But something is better than nothing.
* 7524 - bring back some abort messagesKartik Agaram2021-01-153-6/+33
| | | | | | | | | | | Our infrastructure for displaying errors is far more rudimentary in baremetal. Many ways things can go wrong. But making the attempt seems better than not. I'm also making some effort to keep it easy to see what has been copied over from the top-level, by not modifying copied code to use syntax sugar and so on. It may not be an important enough reason to mix notations in a single file.
* 7523Kartik Agaram2021-01-155-4/+18
| | | | | | | | | | | | | | | | | | | | There's a dependency cycle here: - draw-grapheme (Mu) uses read-grapheme (Mu) to be unicode-aware. - read-grapheme uses read-byte (SubX). Streams are a fundamental data structure in Mu. For the Mu compiler to be able to reason about the safety of stream operations, they need to be an opaque type. All stream primitives are written in SubX. To manipulate a stream's internals we force people to reach for SubX. That way if there's no SubX code there's confidence that things are safe. - read-byte and other stream operations have unit tests, like they should. The unit tests need to print data to screen when say a test fails. To do this they use various check- functions (SubX) that take a string argument. - Printing a string to screen uses draw-grapheme (Mu). Perhaps I should maintain variants of drawing primitives that operate only on ASCII.
* 7522 - bring back a few tests in .subx filesKartik Agaram2021-01-155-5/+744
| | | | | | | | Even though baremetal has tests in SubX, they can only run in Mu programs since the test harness is currently in a Mu layer. Baremetal isn't really intended for running SubX programs at the moment. Is this a step down the slippery slope towards C compilers that I complained about in http://akkartik.name/akkartik-convivial-20200607.pdf?
* 7521 - new plan for testsKartik Agaram2021-01-1511-78/+124
| | | | | | | | | | It's not really manageable to make the fake screen pixel-oriented. Feels excessive to compare things pixel by pixel when we will mostly be writing text to screen. It'll also make expected screen assertions more difficult to manage. So I'm not sure how to make assertions about pixels for now. Instead we'll introduce fake screens at draw-grapheme.
* .Kartik Agaram2021-01-141-0/+1
|
* 7519 - baremetal: run all tests on bootKartik Agaram2021-01-136-3/+87
|
* 7518Kartik Agaram2021-01-1310-0/+19
|
* 7517Kartik Agaram2021-01-131-1/+6
|
* 7516Kartik Agaram2021-01-132-20/+11
|
* 7514Kartik Agaram2021-01-131-0/+0
|
* 7513Kartik Agaram2021-01-131-30/+28
|
* 7510 - baremetal: a game of snakeKartik Agaram2021-01-132-0/+107
|
* 7508Kartik Agaram2021-01-134-24/+47
| | | | | | This is the right way to be direction-independent. Don't save the cursor when drawing a single grapheme. Where the next char goes is just a property of the direction-oriented primitives.
* 7507 - baremetal: drawing text down then rightKartik Agaram2021-01-124-1/+204
|
* 7505Kartik Agaram2021-01-121-9/+9
|
* 7504Kartik Agaram2021-01-121-6/+17
|
* 7503 - baremetal: noodling on default VGA paletteKartik Agaram2021-01-123-0/+451
|
* 7502 - baremetal text: better interfaceKartik Agaram2021-01-122-9/+13
|
* 7501 - baremetal: draw text within a rectangleKartik Agaram2021-01-123-0/+96
|
* 7500 - baremetal: bounds-check screen space before drawingKartik Agaram2021-01-124-6/+106
|
* 7499Kartik Agaram2021-01-121-0/+0
|
* 7497Kartik Agaram2021-01-112-87/+82
|
* 7496Kartik Agaram2021-01-111-0/+4
|
* 7493Kartik Agaram2021-01-091-0/+0
|
* 7492Kartik Agaram2021-01-0910-11/+729
| | | | Port some support for unicode to baremetal.
* 7491 - baremetal: draw ASCII text to screenKartik Agaram2021-01-093-0/+41
|
* 7490 - baremetal: draw a grapheme to screenKartik Agaram2021-01-093-0/+86
|
* 7489 - include GNU UnifontKartik Agaram2021-01-095-9/+252
| | | | | | | https://en.wikipedia.org/wiki/GNU_Unifont#The_.hex_font_format http://unifoundry.com/unifont/index.html Since GNU Unifont is covered under the GPL v2, so I believe is this repo.
generated by cgit-pink 1.4.1-2-gfad0 (git 2.36.2.497.gbbea4dcf42) at 2024-11-24 21:34:11 +0000