pictographer
Well-known member
I have some suggestions about the code the "Audio System Design Tool for Teensy Audio Library" generates.
- Include the URL of the GUI tool in a comment in the exported code. This will help people reuse code; it will be especially helpful to people who don't recognize
Code:
// GUItool: begin automatically generated code - Standardize on one single name for the GUI tool, preferably something more specific to the Audio Library than "GUItool". The web page has the full name "Audio System Design Tool for Teensy Audio Library" and the code comments the completely generic "GUItool" name.
- Modify the import parser to ignore what it doesn't understand rather than rejecting with a syntax error.
- Allow importing a file into the GUI via uploading a file.
- Make the URL in the generated file not only visit the GUI, but also prompt to upload the file named in the link. The user could supply the path either by picking it in a file dialog or by following instructions to add it to the URL.
- Document where the source for the GUI tool is if it's open source. Apologies if it was under my nose and I missed it.