-
Notifications
You must be signed in to change notification settings - Fork 82
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
[Feature request]: Xournal++ compatibility #314
Comments
Since Xournal++ for desktop still gets updates (as far as I understood), would that compatibility layer mean butterfly can import xopp files, but if u do something else than reading you have to save it to a butterfly file or would you also be able to export it back to a xopp file? I'd love to continue using Xournal++ on desktop ^^" |
It will be like the svg import/export function. |
Sorry if it sounded like asking for "Xournal++ Mobile 2". That's not what I wanted, I think describing what I'm hoping for by comparing it to the way you can edit .docx documents with LibreOffice makes more sense. |
Yeah, this is my idea. I think when having a second xournal it will limit the things I can add. |
If there's a big pdf update coming, allow me to make three suggestions :D
|
Hi, thanks for your suggestions.
|
|
|
I added
good first issue
Some problems that can occur:
Here are a few rough steps of what to do:
Feel free to contribute to this project and implement this feature. |
I added xournal++ import feature in #527. |
Is your feature request related to a problem? Please describe
It can be difficult to move to a new note taking app if you wrote in xournal++ before.
Additionally the xournal mobile app won't be updated anymore and Butterfly can have a compatibility layer for this.
Describe your feature request!
Add support for .xopp: https://github.com/xournalpp/xournalpp#file-format
Additional context
This is just an idea of what can be added to Butterfly.
Please upvote this issue if you find it useful, so I can know how much interest there is.
If you want to contribute, please read this
Code of Conduct
The text was updated successfully, but these errors were encountered: