Hello everyone! I don’t know if this is something genuinely useful, but it was a fun little project for me to do. I just enabled an in-post firmware reference tool across the forum. When you post some machine code or hardware routines, hovering your cursor over a firmware vector, kernel restart, CRTC register etc will now pop up a card showing its inputs, outputs, corrupted registers, and a short summary of what it does. It works in regular text, inline code, and syntax blocks. To do this, I converted the Firmware Guide from Bob Taylor and Thomas Defoe into json format : cpc-glossary.json (112.5 KB) and then the forum renderer picks the values if it recognizes an entry (from a list of 311) in a post you’re writing. Hover your cursor over the vectors in these snippets to see it in action: inline code: ; Wait for frame flyback to avoid screen snow call &BD19 ; MC WAIT FLYBACK ; Set border ink to bright white ld b, 26 ld c, b call &BC38 ; SCR SET BORDER ret preformatted blocks: ; Switch to 320x200 4-colour mode ld a, 1 call &BC0E ; SCR SET MODE ; Print ASCII character ld a, 65 ; 'A' call &BB5A ; TXT OUTPUT ret ; Query attached joystick directions and fire buttons call &BB24 ; KM GET JOYSTICK ; H = Joystick 0, L = Joystick 1 Any feedback will be more than welcome - feel free to diss it altogether, too!

Oh, this is a nice feature! Let me try… CALL &BB18 CALL &BB18 CALL &BB18 Some remembers CALL &BA0A ? The one that added vertical bars to the whole display? Was that an unintended effect of jumping in the middle of a routine? Edit: Colour me impressed that it works even when quoted or inside a code block!

[imagen] robcfg: Colour me impressed that it works even when quoted or inside a code block That took a little while to fix, but I’m happy with how it works (initial version only worked outside code blocks because code blocks is where syntax highlighting works, too). I thought about doing the same for BASIC as well but it would clash with natural language.

This is VERY cool! Much better than having to go and look up what each jump block does.

Ah, that’s really good to hear. Not being a dev myself, I had no idea if this was going to be useful or just a nice gimmick - as I said, it was just something fun to work on with the forum capabilities :slight_smile: If you’ve got any ideas on how to make it better, let me know!

Oh, that’s amazing. I love it. Great idea!

Already does, unless we mean different things?

10 PRINT "HELLO" 20 GOTO 10 BASIC keywords get hints in code blocks, I think is what is meant?

Ohhh you meant for BASIC, ok. Yeah, that could be done. My first hurdle is, what’s the input material? It was pretty easy to convert the firmware guide into a structured document as you can see in the OP, but what do we use for input with regards to BASIC? Edit: even code blocks would cause problems, because even assembly blocks tend to contain natural language words that happen to be BASIC keywords. This could be solved by using the custom entity when people want to add BASIC listings, like: 10 MODE 1: CALL &BC0E 20 SOUND 1, 478, 50 (note that this is a BASIC code block). However, it would require people to make sure that the code is marked correctly as BASIC. I did the BASIC code blocks when I did the automatic syntax highlighting and, in theory, it’s automatic, but it’s not well-tested -certainly, not by me.

[imagen] Devlin: BASIC keywords get hints in code blocks, I think is what is meant? Done! [imagen] BASIC Hovercards CPCWiki related Soooo following the Firmware Hovercards and after @Devlin 's suggestion, I went ahead and implemented similar hovercards for BASIC keywords! Due to their similarity to natural language I had to limit them to code blocks only: 10 MODE 1: BORDER 0: CLS 20 INK 0, 0: INK 1, 26: INK 2, 6 30 ENV 1, 5, 1, 5: SOUND 1, 239, 50, 12, 1 40 ORIGIN 320, 200: DEG 50 FOR a = 0 TO 345 STEP 15 60 CALL &BD19: REM Sync to vertical flyback 70 DRAWR 100 * COS(a), 80 * SIN(a), 1 80 MOVER -100 * COS(a), -80 * SIN(a) 90 NEXT a 100 LOCATE 1, 24: PRINT "Press any key to reset palette..."; 110 CALL &BB18: REM Wait for keypress 120 CALL &BC02: REM Reset inks to defaults Ta-daaaah! In order for this to work, th…

Tarjetas flotantes de firmware de CPC

General Relacionado con CPCWiki

Gryzor 24 Septiembre, 2026 13:23 11

¡Listo!

Tema		Respuestas	Vistas
BASIC Hovercards CPCWiki related features , cpcwiki , announcement , basic	9	182	2 Octubre 2026
LocoPad, a web-based code editor for CPC devs CPCWiki related announcement , featured	58	1024	27 Octubre 2026
Test z80 syntax CPCWiki related features , cpcwiki , forum	14	202	24 Septiembre 2026
Introducing in-page emulator on Wiki pages! CPCWiki related emulation , features , cpcwiki , wiki , featured	7	250	30 Septiembre 2026
CPC emulation on CPCWiki pages CPCWiki related	4	103	23 Septiembre 2026

Tarjetas flotantes de firmware de CPC

Temas relacionados