View Code? Open in Web Editor
NEW
πΌ Easy to use datasette emulator for the original Commodore 64 π₯οΈ
License: GNU General Public License v3.0
proxysette's Introduction
π Hey, Iβm Davide (/ΛdeΙͺvΙͺd/ )
π Areas of interest: Rust, embedded programming, FOSS, privacy, XR, networking, IAM, accessible software, web development
π Iβm currently studying Computer Science at University of Trento, Italy
π« Feel free to contact me via the sidebar
proxysette's People
Contributors
Watchers
proxysette's Issues
For each new version in production, a release should be created and uploaded on GitHub automatically:
needs to include binary, tools, LICENSE, USAGE.md in a .zip file
needs to include semantic versioning
needs to include automated changelog
Instructions so that people know what to do when loading a game, such as:
pressing the C= button when the software is found
waiting
typing RUN
waiting again
I'm having trouble extracting the .prg
file from a .d64
disk image. I believe we will also need to prompt the user to understand which .prg
to extract and convert.
Badges, authors and whatnot
Should be required by .t64
and .prg
files I believe
The only planned setting right now is the C64NTSC conversion option lol
I feel like the code as a whole can be structured way better by making proper use of Rust's patterns
Contributors should automatically be added to package authors and readme
would be cool, also to include a tutorial on how to play via car cassette adapter or write on tape
hosted on gh pages
I think it would be better if the tool uses semantic versioning properly, so that the version updates both in the codebase, in the repository, in the README badge and in the releases
Somehow converted .wav
files don't have their artist tag modified by the tool
To be done in parallel with the GUI
It would be better if the prints were more cohesive throughout the code and the verbose/useless ones would only show up in debug mode