@macca, so after some wandering through alternatives... I'm thinking I leave the doc generator as is (no constants, structs) unless we detect {Spin2_Doc_CON} as the initial line in a CON section; then all constants and structs from that section are documented. This way, one can mark as many or as few sections as needed, no matter where they are in the source file.
How does this sound in terms of simplicity and opt-in behavior?
I'm using Google's agent AI thingy called Antigravity with some success to develop Spin2 code. the desktop interface is essentially VSCode (but pointed at different extension site). I wanted to have syntax highlighting and all the other features of this Spin2 VSCode extension ... which took a bit of hunting to get the .visx direct from the vscode extension server and manually load it into Antigravity. If anyone else is headed this direction, here is the url to get the .visx directly: https://marketplace.visualstudio.com/_apis/public/gallery/publishers/IronSheepProductionsLLC/vsextensions/spin2/2.10.6/vspackage
@refaQtor said:
I'm using Google's agent AI thingy called Antigravity with some success to develop Spin2 code. the desktop interface is essentially VSCode (but pointed at different extension site). I wanted to have syntax highlighting and all the other features of this Spin2 VSCode extension ...
IT's fun to hear that you got that working.
You might also want to look at P2 Knowledge base MCP. I think Antigravity supports MCPs, so this would give your agent P2 Architecture understanding and a full Spin2/Pasm2 language reference.
Comments
@macca, so after some wandering through alternatives... I'm thinking I leave the doc generator as is (no constants, structs) unless we detect {Spin2_Doc_CON} as the initial line in a CON section; then all constants and structs from that section are documented. This way, one can mark as many or as few sections as needed, no matter where they are in the source file.
How does this sound in terms of simplicity and opt-in behavior?
I'm using Google's agent AI thingy called Antigravity with some success to develop Spin2 code. the desktop interface is essentially VSCode (but pointed at different extension site). I wanted to have syntax highlighting and all the other features of this Spin2 VSCode extension ... which took a bit of hunting to get the .visx direct from the vscode extension server and manually load it into Antigravity. If anyone else is headed this direction, here is the url to get the .visx directly: https://marketplace.visualstudio.com/_apis/public/gallery/publishers/IronSheepProductionsLLC/vsextensions/spin2/2.10.6/vspackage
IT's fun to hear that you got that working.
You might also want to look at P2 Knowledge base MCP. I think Antigravity supports MCPs, so this would give your agent P2 Architecture understanding and a full Spin2/Pasm2 language reference.