by koffeiniker » Fri Nov 07, 2014 5:26 pm
I'd love to have one special feature that likely could be done in mere software:
playlists!
A file to be edited on the USB stick or CF that holds a list of images to be mounted in the Disk-II-emus or smartport.
This would go together with a feature to load a playlist from the CF, permanently or ... temporary.
Temporary would be great ... just for the next boot.
Imagine a Prodos menu that would allow to activate such playlists:
Select the adventure and have all 4 of its disks in the drive 1 list to play, temporarily, on the next boot see the adventure, one boot later ... be back in the prodos menu.
You'd be able to pack all the software sets on your USB that use disk-emulation into one nice menu.
I'd assume the feature to load a playlist would be an assembler call with a filename as string parameter. This would work on DOS or on Prodos depending on one's preferences. Even CP/M would be possible with a bit more work.
All that a menu would do: display some text for each playlist known to the menu (which does not need to be able to read the USB, this could be just configuration) and the name of the playlist. Call that API call to activate it (temp/perm maybe in a register) and then reboot.
This would add some automation to all this image selecting and would give more meaning to the remote control.
Well, at least I may dream, right? ;-)
PS: when using a temp playlist, you might even go so far to: reset to the perm playlist only when the reset is with shift as well, allowing me to stick with the selected temp playlist as long as I want and kick back into the menu with just a special boot, the "preset/perm" playlist might also be just a file with a specific name: this would reduce the memory consumption, you will likely be short of eeprom on the µC.
PPS: you might want to allow saving a playlist from the menu of the cffa
PPPS: once you go this way, many enhancement to the usability can comfortably be coded in any suitable language under any OS.