-
Notifications
You must be signed in to change notification settings - Fork 90
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
Fork JabRef? #483
Comments
this would be great and I would be glad if the development of Docear and JabRef in general would align better. However, if you want to start this project, be aware that it will take quite a while to complete. When we originally adjusted JabRef to be integrated into Docear, it took us weeks. Of course, in the long run, it would be great if we could always integrate the latest JabRef version and also push changes to JabRef. |
Thanks for the hint. For the most part, changes in JabRef are commented with I tried to replicate those changes in JabRef 2.8 in a personal branch: https://github.com/GeorgLink/Desktop/tree/jabref_2.8
These are notes I took during the process, probably incomplete:This hopefully helps anyone who upgrads JabRef and it serves as a reminder to myself.
|
right :-)
wow, amazing :-)
wouldn't it make more sense to use JabRef 3.2 ? https://github.com/JabRef/jabref/releases/tag/v3.2 |
Yes, 3.2 makes sense. But between 2.7 (Docear) and 3.2 are more changes
|
@GeorgLink Any hint on making JabRef 4.0 work for Docear? I feel you may be able to use submodule method to bring the fork of JabRef to Docear in a better way. But I have no experience with Docear development neither I can find a proper document to start with. Your branch link has been deleted on Github. Can you take a trial and I will follow up if I figure out what I can do for this direction. Thanks! |
Hi @i2000s , Sorry, I cannot help. |
@GeorgLink No worry. My trial didn't work for now, but I'll wait for the Docear team to update JabRef when they have enough people. Thanks. |
@GeorgLink What a pity that your fork is not available any more. Think, the work is lost? If not, it would be helpful if you pushed your work to a branch here. Meanwhile, I quickly sketched a data model how to store a (simple) mindmap inside JabRef (see koppor/jabref#433). Maybe, someone can step in here and work on it? |
Thanks for your interest.
Unfortunately, I don’t have a backup anywhere.
|
In response to #480 (comment).
JabRef moved to GitHub and we could fork the project to maintain our adjustments (separate branch?), create pull-requests for enhanced features to contribute back and regularly pull changes and updates.
Hopefully this would make it easier to import new features and bug fixes from JabRef into Docear.
Thoughts?
The text was updated successfully, but these errors were encountered: