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

Configurable data folder #59

Open
benjamin-heasly opened this issue Jan 6, 2017 · 0 comments
Open

Configurable data folder #59

benjamin-heasly opened this issue Jan 6, 2017 · 0 comments

Comments

@benjamin-heasly
Copy link
Collaborator

benjamin-heasly commented Jan 6, 2017

We currently have configurable folders for toolboxes, projects, and local hooks. This is sufficient for many toolboxes and projects.

For others, it might be useful to have a separately configured "dataRoot" folder, where toolboxes and projects can look for input data and/or write output data. This would allow toolboxes and projects to establish conventions for how their data should be organized, but without having to worry about where the data were located on the local file system.

Implementing this would have a few parts:

  • new comments in sampleStartup.m to help users specify their own data folder as a Matlab preference
  • new code and documentation in tbParsePrefs for a new dataRoot parameter
  • a new utility tbLocateData() to obtain the currently configured data root as a one-liner. This should accept a prefs struct, similar to tbLocateToolbox() and tbLocateProject().
  • tbLocateData() should be mentioned in the wiki page about writing local hook templates, as a way to dynamically choose sensible defaults
@benjamin-heasly benjamin-heasly changed the title Configurable data folder? Configurable data folder Jan 6, 2017
@benjamin-heasly benjamin-heasly modified the milestone: v0.3 Jan 9, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant