Closed prospectoria closed 9 years ago
In this example are the fields really from different tables or is it purely cosmetic?
... and do you care if it was no longer a select/option field? These things are not really supported by select. It could be done with HTML/JS/CSS but then harder to get good mobile/pad support. Is mobile/pad support important?
The fields are all from the same table, but there are so many of them, we need to group them to make them a bit easier to scroll through. In the end there will be 3 types, Company, Person and TNS, they are just types of fields in the overall record. Ideally, I can just update my server side code that spits out the list of fields to include a "label" type of field that will be used as a non-clickable header in the field list.
Also it does not matter if it is no longer a select/option field, also mobile/pad support is not important at this point.
This is also completed, per spec. Specifying * in the label causes a "header" for the group to appear. Something that might be nice (for some other future release/issue) is the ability to put HTML, or otherwise specify the color for the label so they stand out more from the list.
The gwt-Listbox where the fields of the table are displayed, needs to be able to be passed a list that will be displayed in groups, with a group header. The group header will not be selectable, only the fields within the groups can be selected. Ideally we will pass in a list of key/value pairs (via ajax call), the key being the actual field name used to construct the query, and the value being text/HTML that is displayed in the list. It would look something like:
Company - ( heading not selectable) ------------ - ( heading not selectable) Name - (selectable) Address - (selectable) Phone - (selectable)