Auto export on save - #1823
Open
Nxllpointer wants to merge 4 commits into
Open
Conversation
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
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.
Hey there!
I really enjoy using Rnote, however I find it very difficult to embed Rnote documents elsewhere.
Think adding a Rnote sketch to a GitHub README / any other markdown file,
or for my use case, embedding Rnote annotated PDFs into typst documents.
To make other programs ingest Rnote documents, they first need to be exported to common file formats, manually, on every modification of the document.
Yes, one could create a CI workflow to automatically export the document using
rnote-cli,or set up a file system watcher to invoke
rnote-cli exporton every modification,however that is very clunky, or just not applicable for other uses.
This pull request adds a new document-level setting, to automatically export the document as <basename>.svg on every save,
making it very easy to embed the document in other places, and avoids the document and export drifting out of sync.
Im not deeply familiar with the codebase and no GTK wizard, so I oriented myself on existing implementations of settings rows, hope the implementation is decent.
I would love to hear your feedback on this and my current implementation, and hopefully get a feature with this purpose added to the upstream project.
Thanks!
This pull request was written by hand, by myself only.