Update pixelmatch-cpp to match the current JavaScript implementation

Open
#10 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
cpp, javascript

Research direction

Compare the existing pixelmatch-cpp implementation with the current JavaScript pixelmatch 7.2.0 implementation, focusing first on the color-difference metric. Determine the scope of porting OKLab + HyAB and other changes; done would mean matching JavaScript diff results for the same images and configuration.

Written by the indexing model from the issue text.

Description

question

Hi,

I noticed that pixelmatch-cpp appears to be based on an older version of the JavaScript implementation and is no longer fully aligned with the current pixelmatch.

The current JavaScript version is 7.2.0, while the C++ implementation still appears to use the older YIQ-based color-difference metric. The current JavaScript implementation has since moved to OKLab + HyAB for color comparison.

This raises a couple of questions:

Is there a plan to update pixelmatch-cpp to match the current JavaScript implementation?
Is behavioral compatibility between the C++ and JavaScript implementations a goal?
If so, would it be possible to port the newer color-difference algorithm and other changes from the current JavaScript version?
In particular, it would be useful to have the C++ implementation produce the same diff results as the current JavaScript implementation when given the same images and configuration.

I'm interested in using Pixelmatch from a native C++ application without requiring Node.js, so having a current C++ implementation would be very useful.

Thanks!

Dominant language
C++
Stars
48
Forks
12
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.