thanks for the offer. That sounds reasonable. I think this is one of the most requested changes for the addon. So if you are willing to invest some time into this - feel free to do so. I will help as best as I can.
The status quo of the addon is that it only supports CUBA 6 UI APIs. This means in particular, that is bound to the concept of Frames. In CUBA 7 the introduction of the successor of the Frame is a Fragment. Currently the fragment is actually a wizard step.
I think this is actually a problem. Perhaps instead it should be more like “a wizard step contains a fragment” in the sense of such an XML description:
This way it is easier to use the 7.2 functionalities of fragment properties, which would otherwise hard to achieve.
Another problem is that the API of the wizard addon does not really embrace the API style of CUBA 7. In CUBA 7 there are a lot of “Install delegates” or “event handlers” via the corresponding annotated methods.
But this also requires further investigation and is actually not really needed in order to leverage the CUBA 7 APIs.
So in order to achieve a bare bone compatibility with the CUBA 7 UI API, I think it might be enough to try to replace the superclass of the AbstractWizardFrame from AbstractFrame to Fragment. See: https://github.com/mariodavid/cuba-component-wizard/blob/master/modules/gui/src/de/diedavids/cuba/wizard/gui/components/AbstractWizardStep.java
Then you have take a look at the corresponding errors that might occur. I have not really looked into what might come up from this, so it is hard to judge right now.
To try it out, you can look into this example: https://github.com/mariodavid/cuba-example-using-wizard
Note, in order to test it locally, you need to install it via
I hope this helps as a starting point.