Draft
Conversation
Contributor
|
Dev meeting: it'd be nice to have a test script for this one, or at least scripter-friendly documentation on how to use it |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
digisomni
added
the
dormant
|
Hello! Is this still an issue? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is an initial working version of a data export API for Interface scripts to use. It's a bit dangerous since it can of course write (or overwrite) files on the system of a specified name and path... so the way I set it up is that the actual path and filename can only be set by the user using a Qt/QML dialog. Once set, all scripts can write to that path.
I think what's missing still is a reset function to stop scripts from mucking with your export after you've completed it.
Generation 2 should consist of: a per-app export API that allows you to set paths per-app that persist restarts. (this would of course have to use the private context in order to prevent scripts from altering the paths.)
Generation 3 should consist of: a per-app limited storage based on path+filename/URL+filename. Maybe a 512KB data limit would be good with mayhaps a permission dialog opening to say the app wants to have its own space to write to that sits in the Vircadia appData folder.