You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Offering an easy migration path for projects porting from JAI
Removing JAI references from documentation and API to prevent confusion
My best idea is to deprecate methods and classes that reference JAI while introducing ImageN replacements:
public class ImageN {
// JAI Core
protected static final int HINT_IMAGE_LAYOUT = 101;
...
public static RenderingHints.Key KEY_IMAGE_LAYOUT =
new RenderingKey(HINT_IMAGE_LAYOUT, ImageLayout.class);
}
/**
*
* @deprecated Use ImageN
*/
public final class JAI extends ImageN {
....
}
There is also something to be said for just just going directly to ImageN.
The text was updated successfully, but these errors were encountered:
I am not quite sure how to balance between:
My best idea is to deprecate methods and classes that reference JAI while introducing ImageN replacements:
There is also something to be said for just just going directly to ImageN.
The text was updated successfully, but these errors were encountered: