I have small entities that I do want to be edited inline in a table instead of havin an Editor screen with only two fields.
I created a Lookup screen with an inline editable table to do so following advices here.
Then I wanted to add a windowActionsFrame as we can find in Editor screen to have “ok” & “close” buttons (Lookup screens do not have buttons as you know). I need that because my screen is a dialog and a dialog without buttons is strange.
But then CUBA complained that it can not find “windowCommit”. I guess that standard windowActionsFrame can not be put in Lookup screens because only Editor initializes windowCommit and windowClose actions.
I then tried to derive the screen from Editor instead of Lookup. But then it complains that it cannot find a main Datasource. Which is true as the main component (the table) uses a collectionDataSource. And I cannot change it to main Datasource because table needs a CollectionDataSource or equivalent.
So I finally built manually myself a frame with ok and close buttons invoking appropriate Window methods commit() & close(). This is a bit annoying to bypass the framework, because everything needs to be redefined manually : messages pack, keyboard shortcuts, decsriptions, etc.
Was there another solution that I missed ? If the answer is no I will (try to) create a template with my screen.
That would be great to be able to put the windowActionsFrames outside of an Editor screen (e.g allowing it to work with collection datasources).
Beyond that, the use case “entities edited inline in a table instead of having a dedicated Editor” could be a template in a future Studio version. This is a common use case.