Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Data files for modules should be treated differently than resources #2

Open
jadkik opened this issue Aug 5, 2013 · 0 comments
Open
Labels

Comments

@jadkik
Copy link
Member

jadkik commented Aug 5, 2013

Resources for the modules are generally static files which could be used inside the application, such as images, icons, etc.

Data files are files generated by modules for the use of the user, or data specific to this setup and/or user.

Currently, data files, if used, are saved alongside the resources, using the same interface.

However, it is not guaranteed that the resources are in a writable directory. Depending on the setup, modules could be distributed in egg files (archives), directories with write access (~/.config/coinbox/modules for example), or directories without write access (/usr/share/coinbox/modules).

For this purpose, data files should be stored in a custom location defined in the configuration file, or in a command-line argument. Sensible defaults should be set depending on the platform/environment.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant