Search component

[ebruchez]

The purpose of the Autocomplete control was initially just that: do some automatic completion based on a search service.

But users have been using it to do something more akin to a search, and unfortunately this only works in some cases. In the general case the Autocomplete control is not appropriate because it requires storing the label and value returned by the service.

We would like to consider a control more appropriate for searching. The control could open up a popup, like the GitHub selectors. It's probably best to have the search field in that popup rather than in the form itself, because that clarifies the selection process: open, search, select, commit.

This should be configurable to call a service to which the search string is passed. It would return possibly multiple "rows" of data with "columns" to display in the search popup. For large datasets, we could imagine paging/sorting, but that's P2.

Selecting values would use values from one column, or possibly multiple (TBD).

The screenshot is just an example of popup, not necessarily of what the Search control would look like.

See also #1433.

+1 from customer

[ebruchez]

+1 from customer for a search component for lots of items

[orbeon]

+1 from evaluator

[ebruchez]

+1 from customer

Also requesting multi-line entries with richer formatting (such as bold).