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.

Sign up for GitHub

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

Jump to bottom

Sort out CodeLocation and JarvisConfig in relation to Jarvis.dws Autostart #35

Open
bpbecker opened this issue Oct 8, 2022 · 0 comments
Open

Sort out CodeLocation and JarvisConfig in relation to Jarvis.dws Autostart #35

bpbecker opened this issue Oct 8, 2022 · 0 comments
Assignees
@bpbecker
Labels
enhancement New feature or request

Comments

@bpbecker
Copy link
Contributor

bpbecker commented Oct 8, 2022

Currently, if Jarvis is loaded using the Jarvis.dws workspace, relative file paths are determined from the workspace location. This has some implications for the dyalog/jarvis container because it uses that workspace. I believe a more flexible (and user friendly) solution would be to use the location of the JarvisConfig file, if it exists, as the root folder from which relative folders are found. This makes Jarvis apps more portable.
@bpbecker bpbecker added the enhancement New feature or request label Oct 8, 2022
@bpbecker bpbecker self-assigned this Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bpbecker bpbecker

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bpbecker