Hello reviewers,
We are building an open source, application platform for creating tools that linguists and translators will use for translating the Bible to any language. To simplify user support, we are trying to stick with a single directory structure across Linux, Windows, and macOS where user data and settings will be stored. We would prefer to not need to instruct users to manually connect the directory when they install the snap.
- name:
platform-bible - description: Extensible software platform used to build Bible translation tools
- snapcraft: We’re using
electron-builderso there isn’t a full snapcraft file available, but here is the relevant electron config for thepersonal-filesinterface we’re requesting. - upstream: GitHub - paranext/paranext-core: Electron client, extension host, and C# library for Paranext
- upstream-relation: I am one of the developers working on this project.
- interfaces:
- personal-files:
- request-type: auto-connection
- reasoning: Our software is intended to run on Linux, Windows, and macOS. The application directory that stores user data and settings has been standardized across all OSes to be the
{USER_HOME_DIRECTORY}/.platform.bible. We may need to distribute the application in Linux on forms other than a snap, so we want to make sure the snap is able to read and write to the actual directory within the user’s home directory. Also, we don’t want user data to be lost if they remove the snap and have not uploaded it somewhere.
- personal-files:
Note that if this is approved, I will have one more, similar request in the near future for another tool built on top of this framework.
Thanks, Matt