Split up some of the bridge files, as their sizes are getting out of hand

Open
#279 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@balazs-szucs is already working on this.

Since Nov 13, 2026.

Assessment

This issue has not been assessed yet.

Description

See title.

Having large files makes it hard to reason about changes. Some files have grown quite large, and their current organization makes certain changes difficult, as it's not always clear what's where or how everything is connected.

Some of this is expected for a codebase like JPDFium, especially with native API declarations and Java FFM bindings or cpp bridges. Wrapping a large native API can add up to a lot of LOC, even when the individual wrappers are fairly straightforward. (meaning: the function they are wrap doing bulk of "difficult work") Still, I'd like to separate that unavoidable bulk from code that could be split up or organized more clearly. I think I can make something work.

Dominant language
Java
Stars
16
Forks
4
Avg merge
2d 2h
Merged PRs (30d)
56

Getting set up

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.

More from Stirling-Tools/JPDFium

All issues in Stirling-Tools/JPDFium

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.