Formatting: Update dev notes so that Todo Tree VS Code plugin can find todo entries
This commit is contained in:
parent
549e0dc73c
commit
50741ba038
|
|
@ -1,8 +1,8 @@
|
|||
# Dev notes — 2023-08-05
|
||||
|
||||
- consider refactoring assembler to do something more like 'tokenize, then call helper functons'
|
||||
- [ ] consider refactoring assembler to do something more like 'tokenize, then call helper functons'
|
||||
|
||||
- consider an extended system:
|
||||
- [ ] consider an extended system:
|
||||
- add a byte in the ~zero-page to act as a flag for display mode
|
||||
- 0 = 1 byte per pixel (default)
|
||||
- 1 = 1 bit per pixel
|
||||
|
|
@ -20,7 +20,7 @@
|
|||
- but permit gamepad since that's a subset (NES layout = 8 bits/bytes, depending on mode)
|
||||
- look at how uxn does it?
|
||||
|
||||
- <mark>TODO: rewrite to call things 'opcodes' and 'operands'</mark>
|
||||
- [ ] rewrite to call things 'opcodes' and 'operands'
|
||||
|
||||
- add bank switching for higher 128 bytes
|
||||
- add a flag in the ~zero-page
|
||||
|
|
@ -28,4 +28,4 @@
|
|||
- try writing:
|
||||
- a 'greater than' routine
|
||||
|
||||
- make coding forms!
|
||||
- [x] make coding forms!
|
||||
|
|
@ -18,7 +18,7 @@ and <mark>overflow is signed</mark>
|
|||
|
||||
### flags register
|
||||
|
||||
Replace the current 'Carry Flag' with a Flags Register.
|
||||
- [ ] Replace the current 'Carry Flag' with a Flags Register.
|
||||
|
||||
Here's a sketch for the bit pattern:
|
||||
|
||||
|
|
@ -45,7 +45,7 @@ cf. 6502:
|
|||
|
||||
### flag opcodes
|
||||
|
||||
- <mark>TODO:</mark> replace `CHP` and `CFC` with `FHP` and `FTG`
|
||||
- [ ] replace `CHP` and `CFC` with `FHP` and `FTG`
|
||||
|
||||
- `FHP n`: hop if flag _n_ is set
|
||||
- eg: `FHP 0` = hop if carry flag set
|
||||
|
|
|
|||
|
|
@ -61,7 +61,7 @@ Z X C V
|
|||
## Turtle graphics
|
||||
|
||||
- yesterday Elizabeth had the great idea to create a turtle robot to go with the paper computer
|
||||
- a minimal LOGO would be a fantastic (if challenging) program to write for the computer
|
||||
- [ ] a minimal LOGO would be a fantastic (if challenging) program to write for the computer
|
||||
- it could use the hex keypad:
|
||||
- using CHIP-8 layout...
|
||||
- A key: mode toggle
|
||||
|
|
@ -78,4 +78,4 @@ Z X C V
|
|||
|
||||
## Dot-matrix display
|
||||
|
||||
- Maybe try 5x5, like the micro:bit?
|
||||
- [ ] Maybe try 5x5, like the micro:bit?
|
||||
|
|
@ -1,6 +1,6 @@
|
|||
# Dev notes — 2023-08-10
|
||||
|
||||
- Name it "Cardiograph"
|
||||
- [x] Name it "Cardiograph"
|
||||
- homage to CARDIAC
|
||||
- (and cardboard)
|
||||
- and the special feature is that unlike other paper computers, this one has a graphical display
|
||||
|
|
@ -9,9 +9,9 @@
|
|||
|
||||
## Keypad (and memory map)
|
||||
|
||||
- Copy the CHIP-8 approach: one memory location that stores the current key pressed
|
||||
- (Only one key can be pressed at a time)
|
||||
- And then do a bitmask-y thing for the secret advanced mode, to add the ability to detecut multiple simultaneous keypresses
|
||||
- [ ] Copy the CHIP-8 approach: one memory location that stores the current key pressed
|
||||
- (Only one key can be pressed at a time)
|
||||
- And then do a bitmask-y thing for the secret advanced mode, to add the ability to detect multiple simultaneous keypresses
|
||||
|
||||
## Display (and memory map)
|
||||
|
||||
|
|
@ -29,4 +29,4 @@
|
|||
|
||||
## (Moved from readme:) Possible features, maybe someday
|
||||
|
||||
- Timer (for a version in software/electronic-hardware)
|
||||
- Timer (for a version in software/electronic-hardware)
|
||||
Loading…
Reference in New Issue