RFC-3: Enhance EhBASIC?

[netzerohero]

Hello Rumbledethumps and the Picocomputer community.

I'm hoping to encourage thoughts and discussion on enhancing EhBASIC for the picocomputer system.

Rumbledethumps has an initial ehbasic repo in the picocomputer Github project. (Thank you!)
And he has built-out two fundamental picocomputer capabilities: SDK/file-io and VGA-graphics. (Thank you!)

Is there an interest in bringing BASIC-program file SAVE/LOAD and graphics-support to EhBASIC?

1. SAVE / LOAD: EhBASIC, written in assembler, has the hooks for SAVE / LOAD from the BASIC-prompt. rp6502-sdk provides file-io within C. Adding SAVE & LOAD would enhance EhBASIC's user experience.

2. BASIC-Graphics: Adding point and line plotting graphics to EhBASIC would open-up the picocomputer's EhBASIC to a wealth of BASIC code available from the retro-computer domain. Unclear to me how adding plot and line graphics that might be approached within EhBASIC. Historically BASICs "back-in-the-day" provided 'USR hooks' to assembly routines. EhBASIC appears to also provide USR() functionality.

And importantly from my perspective (as I am new to Git / Github, but know the importance of good CM practices) is the setup and management of repo workflows:

3. CM-Workflow: How should the two above candidate enhancements be tracked/organized within this project or set-up in another git-hub project? (e.g., github issue in the ehbasic repo, git forks/branches, pull-requests etc.)?

Thank you for your consideration.