@mario quick question is there any chance to get the Wizard addon updated to version 6.10.X? getting some errors when trying to import the addon as it is released for 6.8 only. Is that possible?
Also, I’m not able to get access to the sample project in Git, I’m getting this error: Unable to load app component… Please check credentials of project repositories.
Hi, while you’re waiting for the author’s response, try to clone the original addon locally, and open it in Studio. Then you can try to simply upgrade the CUBA version, assemble it and install as a local component on your machine. If it compiles without errors, there’s a chance that you can use it as is in your project.
You’re targeting 7.1.0 Beta version (I see it in the screenshot), and there are no add-ons yet for that version…
If you want to test a Beta/Snapshot version of CUBA, you can’t use any add-ons compiled for a stable version.
Downgrade the project to the latest stable CUBA 7.0, and you’ll be able to install the Wizard add-on version 0.4.0
I’m attempting to use Wizard in my project after previous failed attempt few months ago. I just create a step and trying to get it working.
How to work with data containers in wizard step? I have created the data container (companyDc) in the main screen and referring that in the step. But it shows me that companyDc not found.
I have checked your sample project, where data sources are used, not data containers. So How do I make it working with data container?
Few observations:
CUBA IDE warns that UI Descriptor not found, which is there. If I make this class extending Screen instead of AbstractWizardStep, this warning will go away, but that will not work with Wizard.
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.
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.
Thanks for the guidance @mario. I have started with forking with your git hub repository. Coming week I will start slowly working on this. Anytime I do have doubt will ask you clarifications.