Becky on Nostr: I think it’s definitely a good idea to have some sort of text output available as ...
I think it’s definitely a good idea to have some sort of text output available as soon as the machine boots up.
I also really like the shadow text buffer idea you were working on. It takes care of a few problems, especially if we would want to have a C64 or Atari 800 built-in editor, which I think would be pretty awesome.
What if we split the text output into two: (a) a driver that includes a basic CHROUT kind of thing plus the vblank-driven redisplay of the buffer. Part (b) would be to implement ANSI control codes.
‘A’ would also need a driver-level way of moving the cursor and setting the current text attribute, but at this level, that should be routines we can JSR to, not interpreting control codes.
If you’re still ok doing ‘a’, then I can code up ‘b’. (I’d have to wait until your driver is done though.)
I also really like the shadow text buffer idea you were working on. It takes care of a few problems, especially if we would want to have a C64 or Atari 800 built-in editor, which I think would be pretty awesome.
What if we split the text output into two: (a) a driver that includes a basic CHROUT kind of thing plus the vblank-driven redisplay of the buffer. Part (b) would be to implement ANSI control codes.
‘A’ would also need a driver-level way of moving the cursor and setting the current text attribute, but at this level, that should be routines we can JSR to, not interpreting control codes.
If you’re still ok doing ‘a’, then I can code up ‘b’. (I’d have to wait until your driver is done though.)