kinow commented on PR #254: URL: https://github.com/apache/commons-imaging/pull/254#issuecomment-1352724001
>In my understanding, the alpha phase allows large API changes, but after entering the beta phase, the API tends to be stable, and there can be some minor damage, but usually it should not change as much as the alpha phase. Correct. That's why it's important to decide on whether it will be an alpha3 or beta1. I didn't have plans to add anything to the public API before 1.0, but I think WebP support could go in any non-final release as long as we take care with what is added to the public API, and add tests/docs. >However, even if this problem is solved, I think the commons-imaging API still relies too much on AWT. Agreed. >I don't think so many BufferedImage based APIs should be provided, nor should the implementation of each format be based on AWT/Swing. > >Maybe we can provide a general abstraction to hide these details. The implementation of the format should only use a common interface, and behind the interface may be AWT/Swing, JavaFX, Android, or even other file formats writter. > >This is my rough idea. Do you have any opinion on it? Hmmm, this sounds interesting! I just remembered that when I went looking for ways to support Android, I found someone that had a project with the `library-something.jar`, with the interfaces, and `library-something-awt.jar` and `library-something-android.jar`. But I found that solution harder to implement & maintain. But let's give it another try before the 1.0. I don't mind postponing this release in order to have more alphas/betas. This is the issue for Android, we can rename/use it for AWT: https://issues.apache.org/jira/browse/IMAGING-208 (if you do not have an account, let me know and I'll prepare the sign up process for you, ASF blocked new sign ups due to Spam). Thanks!!! -Bruno -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
