api: separate out AWT dependent parts (2.x) #338
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation and Context
There is still a small amount of AWT usage in the API module that is blocking Android usage. It is mostly around BufferedImage, and is located in two areas - the EmbeddedImage support for ST 0903, and the ST 1909 metadata overlay.
This refactors the API module to avoid that. Its a breaking change, suited to 2.x.
Resolves #332.
The Android build support (#253) needs significantly more than this, but its a step forward.
Description
The ST 0903 embedded image becomes a byte array. The user can invoke ImageIO if needed.
The ST 1909 rendering support moves to a new module (api-awt).
I'm not tied to the module name or namespace - feel free to suggest or modify as required.
How Has This Been Tested?
Full build.
Tested overlay still works OK in the viewer application.
Screenshots (if appropriate):
Types of changes
Checklist: