|
Top-level
 So a few days I've realized that I very much liked working using structured editing. Structured editing means that your editor is aware of the program's functioning enough that it handles how it should be presented, so you're not editing text as much as the underlying structure of the program. It's just a fancy way of saying that it's basically just a symbols aware disassembler. I've spent the past 2 days improving the UX so I could run the reassembler without going through the terminal. 13 comments
Assigning a type to a label(just a suffix extension in this case) allows me to display its content in whichever way I need(as opcodes, as letters, as hex bytes, or ..)  
[DATA EXPUNGED]
@prahou that's cream, the smalltalk font with slights modifications. You can grab it here: https://git.sr.ht/~rabbits/left/tree/main/item/etc/cream12.uf2
[DATA EXPUNGED]
 @neauoire it was common for early Lisps (eg Acornsoft Lisp on the BBC Micro) to come with a structure editor, as they are very compact in Lisp. It was also common, and fun/dangerous, to extend the primitive structure editor with extra commands, by editing it. with itself of course! |
Gregory's Server
(the code formatting in the video is all messed up, it's the first time that I manage to connect all 3 parts of together and I was too excited to bother fixing up the syntax parser)
The two hexadecimal editors are:
- left: a rom file(binary blob with the bytecode)
- right: a symbols file(label names and comments)