Yes, I agree this is needed. I had started doing this for *viewers*, see
dash:ValueTableViewer. But there is no symmetric concept for editors. I
have used the term "aggregate viewers" so we could call them "aggregate
editors" too. I have no strong opinion - do you prefer "compound"?
Also I guess we could introduce a marker property to indicate (in the
RDF model) that such widgets have a different meaning that other,
single-valued ones. What about dash:aggregator true or dash:compound
true as a flag?
Holger
On 12/06/2020 20:55, Tomasz Pluskiewicz wrote:
I notice a little asymmetry in the editor/viewer widgets.
I would like to suggest adding a "compound editor". Such an editor
would apply to the property and all of its values. An example of such
an editor would be a multi-select combobox.
Tom
--
You received this message because you are subscribed to the Google
Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/a36d83f7-741a-4db8-8f95-498ba5d635f8o%40googlegroups.com
<https://groups.google.com/d/msgid/topbraid-users/a36d83f7-741a-4db8-8f95-498ba5d635f8o%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
You received this message because you are subscribed to the Google Groups "TopBraid
Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/topbraid-users/8e5fe936-625a-d03d-3761-e3dd851b4aa4%40topquadrant.com.
