Storage

[jiahuahl]

App needs a database-like ability to store the media we want to play.

start with audio and pictures

for each piece of audio or picture we need to remember:

• path to media
• a list of aliases (strings that is the 'name' of the audio) [e.g. "roblox_oof", "roblox_hurt_sound", "oof"]
• a list of tags (strings that we can use to filter results) [e.g. "roblox", "damage", "funny"]
• time last played
• total times played

for audio we also need:

• volume to play at

data must persist after app is closed and reloaded automatically upon restart.

for the future it'd also be good to be able to export this database so you can easily migrate to another machine without having to redo everything.

[rwblickhan]

Why don't we just keep a register of filepaths to directories we want to include?

[jiahuahl]

Why don't we just keep a register of filepaths to directories we want to include?

that's a good idea, but i think it doesn't replace the functionality outlined by this ticket. that should be another feature later down the line.

we need to store info about each particular file in order to search them by alias or by tag, just remembering the directories will not be enough. Including the filepath to the directory is more of a way for the user to specify what media they want to add (i.e. scan this entire folder for files), but this ticket is about the app's knowledge of the media once we've already added it.

[rwblickhan]

Yss as h I realized that after rereading this. Still cautious about storing a “database” - we should probably just keep a file serialized on disk that we ocassionslly wrote back put

[rwblickhan]

for the future it'd also be good to be able to export this database so you can easily migrate to another machine without having to redo everything.

not trivial unless we copy all of the files into a central location (maybe not terrible?)