i’ve a general question about the extensibility of the screen XML definitions. I read your blog post about how to integrate external UI components which is great.
Nevertheless i thought of another probably more tighter integration into the application, especially into the screens XML definition.
Let’s take Yuiry’s example about vaadin-wizard-example which uses the corresponding vaadin addon. The integration is slightly easy because it’s already a vaadin add-on.
But what i thought of is the following. Let’s assume i want to be able to write in my XML editor screen definition like this:
<wizard id="myWizard"> <step id="myId"> <fieldGroup id="fieldGroupWithFirstFiveAttributes"> </step> <step> <fieldGroup id="fieldGroupWithSecondFiveAttributes"> </step> </wizard>
because i want to provide the same ease of use or the same programming model to my application as i already have with other CUBA components.
My general solution to this problem would be to ask here if this can be added to the platform. This is fine, but probably will not always a success. Therefore my question is, if it is at all (with a reasonable amount of time) possible to extend the screen.xml definition?
I don’t even talk about studio integration of these extensions but more of how i get another completely new component into the application? I saw window.xsd as a starting point, but it would be great to illustrate a walk through the different building blocks on how to achieve something like this.