Oxygen XML Forum

We are currently using a Java-based plugin with JFrame and customised Swing components, compiled with Java 8, in Oxygen 24.1. Now, we have to update to Oxygen 26. While backward compatibility allows the plugin to open without issues, we’ve noticed inconsistencies in UI sizing and alignment for some Swing components within the editor.

Could you advise on how best to handle these UI discrepancies? Specifically, we’re considering upgrading the plugin to Java 17 to better align with Oxygen’s Java version, and we’d like to understand if this upgrade should be prioritized or if there are alternative adjustments for Java 8 compatibility within Oxygen 26.

Thank you for any guidance you can provide.

Hi,
I do not consider that compiling your plugin with Java 17 instead of Java 8 will make any difference. As you did not give me enough information about the visual discrepancies I'm not sure how to help further. I think the problem stems from the way in which the UI was built in the Java code, maybe from what layout manager was used.
Regards,
Radu

We are using custom components extended from default ones. As an example we have a custom button extended from JButton and it renders as follows:
Oxygen 24: Oxygen 26: we would like it to be uniform across both the versions

Hi,
We have an API class "ro.sync.exml.workspace.api.standalone.ui.OxygenUIComponentsFactory" which allows developers to create UI components which look similar to Oxygen's ones. Maybe you could use for example "ro.sync.exml.workspace.api.standalone.ui.OxygenUIComponentsFactory.createButton(Action)".
Other than that, there seems to be a baseline problem with your button, I do not know why that is as it's a custom button. our technical support does not cover debugging how various custom Swing components are implemented.
Regards,
Radu