| Customize the UI for the GWC / Front End Protocol | |
User Agents send form data to form data processing agents as a sequence of control-name and control-value.
For example, the browser sends pairs of name=value to the GAS. Most controls have names, but the value submitted is not always the one expected. Inclusive form is introduced to workaround the default behavior.
control-name=control-valuethat is <prefix> [ container ] = [ [ ss/prefix ] <value> ]
control-name/control-value=that is <prefix> [ container ] [ / [ ss/prefix ] <value> ] =
Where
prefix is a character to identify the type of action.
container is the component identifier.
ss is a subprefix.
value is the value expected by the GAS, which is not always the default value that a User Agent sends.
To build the control-name, use the template paths IDID (inclusive form) or XDID (exclusive form).
Facilities are available as functions in the Front End Protocol Functions section.
Exclusive form:
<input type="radio" gwc:attributes="name XDID; value ID;... />
produces <input type="radio" name="a" value="89"... />
Inclusive form:
<input type="submit" gwc:attributes="name IDID"... />
produces <input type="submit" name="a/89"... />