Migrate yFiles dependency to a newer version
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
Start by locating the yFiles 2.x dependency and its Java Swing integration, then evaluate a current yFiles release with access from yWorks. Review the migration differences and vendor guidance before changing the integration; done means Bindiff builds with the current fully licensed yFiles version and retains its existing functionality.
Written by the indexing model from the issue text.
Description
This project has a dependency on an outdated version of the commercial graph visualization library yFiles (for Java Swing).
Developers were able to get a time limited evaluation version of the library ever since Bindiff was released as a GitHub project many years ago.
However, the version being used (2.x) is a very old legacy and is superseded by much more modern, easier to use and more powerful variants. The old version cannot be regularly evaluated, anymore. There has been a newer version of yFiles (3.x) available for many years, now, and there will be yFiles for Java Swing 4.0 coming, in a couple of months.
In order to keep this project alive I suggest migrating from the old version to one of the newer ones (the step from 2.x to 3.x is a bigger step, 4.0 won't be a big step from 3.x). The support team at yWorks (the vendor behind yFiles) would be open to helping with migration issues and would be happy to give away a small bounty for that task, just so that yWorks doesn't need to disappoint all those anymore who request that long-deprecated version of yFiles by all the bindiff developers.
Solution
Evaluate a current release of yFiles, connect with the yWorks folks and tell them that you will be migrating Bindiff and they will be happy to provide you with access to both the old and current versions. Then perform the migration. yWorks will ensure that bindiff can be built with a fully licensed version of yFiles by the maintainers.
Alternatives
If you are looking for a more modern frontend solution. yWorks would be happy to do the same for a "web frontend version" of Bindiff - yFiles for HTML should be a good match, but this is a far more ambitious project that requires a modularization of bindiff into frontend and backend, etc.
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from google/bindiff
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
question
Difficulty 3/5 1-2 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 1/5 Under an hour Newbie friendliness 55/100
-
Difficulty 5/5 Over a week Newbie friendliness 15/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
infinispan/infinispan#18150 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
opensearch-project/k-NN#3597 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100