Add-on file structure

[solbero]

We probably need to decide on a installation file structure for the add-on.

I assume that all of the binaries, libretro cores, and skeleton config files would go into a folder in /storage/.xbmc/addons/. There is some information we could use on the XBMC wiki concerning the structure of this folder. It seems pretty straight forward.

The main choice we have to make, I think, is concerning non-static files and their placement. The zaggash add-on creates a folder emulator in $HOME. However, I am a little averse about cluttering the user's home folder, even though it allows easy access to things like configs, screenshots, etc. We could also use /storage/.xbmc/userdata/addon_data which seems to be the standard placement for non-static files.

What are your thoughts on these issues?

[demsullivan]

For the installed files (binaries, cores, etc.) we could probably just follow zaggash's structure - bin, cores, lib, shaders, etc.

I agree with not cluttering $HOME. addon_data is not a bad idea, or maybe /storage/.emulators rather than /storage/emulators so it's hidden?

[solbero]

I propose the following structure for static files (based on zaggash'):

/storage/.xbmc/addons/script.retroarch-lakka/
/storage/.xbmc/addons/script.retroarch-lakka/bin/
/storage/.xbmc/addons/script.retroarch-lakka/config/
/storage/.xbmc/addons/script.retroarch-lakka/cores/
/storage/.xbmc/addons/script.retroarch-lakka/lib/
/storage/.xbmc/addons/script.retroarch-lakka/shaders/
/storage/.xbmc/addons/script.retroarch-lakka/assets/

Non-static files (such as config, savefiles, savestates, etc) will live in:

/storage/emulators/retroarch-lakka/
/storage/emulators/retroarch-lakka/config/
/storage/emulators/retroarch-lakka/system/
/storage/emulators/retroarch-lakka/save/
/storage/emulators/retroarch-lakka/log/

Screenshots are placed in /storage/screenshots/

[demsullivan]

Sounds good to me.