-
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
Shortest Path to Latest Freeplane and JabRef Release Updates #513
Comments
@zenny You are very welcome to join the development team. JabRef is now more modularized and it should be more easy to port Docear's features to it. In case, you are more into web development: Why not starting a new web-based Docear from scratch? -- We played with that two years ago (https://github.com/JabRef/scimappr), but did not continue (due to lack of funding). |
Hello @zenny and @koppor , |
@xiepenggis Thank you for the update. C# is indeed a very useful skill, since the old Microsoft Word plugin was coded in C#. However, Microsoft seems to switch to JavaScript (JabRef/jabref#6904). Regarding Docear and JabRef. We cannot use the FeeMind-Code anymore as it is licensed GPL. Thus, we need to rewrite the whole mindmap code. This is currently work in progress (refs https://github.com/koppor/jabref/issues/433). First results should be available mid/end october. |
@koppor So excited to hear that, can not wait to try it out. |
Hi,
From #497 (comment)
@Joeran Your efforts are matchless, but a lot of things have changed since the last release, and is breaking many a things, like adding a new project does not get refreshed with a new directory unless Docear (DC) is restarted even in GNU/Linux.
However, it would be appropriate to let the users know the shortest path to upgrade to latest Freeplane (FP) and JabRef (JR) releases componentwise. I meant just the FP and JR binaries which are at v1.7.9 and v4.3.1 resepectively.
Or let users know the conflicts that they may encounter between the DC v1.2Buile291 code and the latest stable FP and JR releases.
Appreciate that!
Cheers,
/z
The text was updated successfully, but these errors were encountered: