Joerg Heinicke <j.heinicke <at> ewerk.com> writes:
> When thinking about it I have to ask whether we need an output widget? Isn't
> it just a matter of styling, but nothing for the form definition (we already
> have wi:field/wi:styling/@type='output'). So shouldn't we remove the
> output widget?
I found a use case for the output widget - or better said a case where I need it
at the moment. But the reason for it is not the output widget itself, but seems
to be a limitation of the binding:
I have a repeater where a list of different objects is put in. These objects
have an ID, which I don't want to put into the frontend (i.e. HTML code, e.g.
hidden input). If I make the ID in the form definition a field (without
mentioning it in the template) the ID is null afterwards. It seems not to be
possible to set the repeater ID to direction="load" in the binding definition:
<wb:repeater id="objects" parent-path="." row-path="objects"
unique-row-id="id" unique-path="@id">
<wd:convertor datatype="long"/>
<wb:on-bind>
<wb:value id="name" path="name" direction="load"/>
</wb:on-bind>
</wb:repeater>
So the only possibility I have at the moment is to use a wd:output, so that the
value of the ID is not replaced with null.
Is this observation correct? Is there an option for the binding to set
direction="load"? Setting it on wb:repeater does not work for me.
Joerg
