Extension:Semantic Forms Select

What can this extension do?
This extension generates a select form element which option values are from semantic query or parser function. Semantic Forms provides useful input type for select elements such as dropdown, combobox, and listbox. Their option values can be derived from a static list, pages in a category, concept, property's allowed values, etc. However, it is still limited. This extension provides these features
 * The option values for select element is from an SMW query or parser function.
 * If the SMW query or parser function is not parametrized, its optioned values are loaded at form generation time.
 * If the SMW query or parser function is parametrized, in another word, its values depend on another form field. Its values are loaded through ajax call when trigger field changes.

Usage
Two form fields are involved. The first one is the form field we are trying to define. It is termed as Select field. The second one is the field the Select field depends on. It is termed as Value field. A change of Value field will trigger the loading of Select field.

The input type from this extension is SF_Select. Field parameters are shown in the table below.

Query And Function format
In the above example, the query is |format=list|sep=,|link=none|headers=hide|limit=5000. To avoid parsing and text transform, we have to convert [ to (, = to ~ and | to ; in the query.

Parser function follows the same rule. The parser function is ask in example above. We can of course use other valid parser function. To fit a parser function into field definition, Strip the at the beginning and the end of normal parser function format.

The result from query or parser function should be a list of string separated by comma.

Examples
Here the getallusers is a custom parser function which gives all users in current installation. The parameter is the special character string @@@@. In this example, the Select field is P2Protocols3. The Value field is Project1. Both Select field and Value field are in the same template since we have sametemplate in field definition. If Value field is from another template, the template parameter should be used. When Project1 field changes, the @@@@ will be replaced by the value of Project1's value. The query is then sent to server through ajax call. The results will be the option values for P2Protocols3 field. if the current template is multiple, the P2Protocols3 only depends on the Project1 in the same instance.
 * Example 1: Static query. The values are retrieved when form is loaded.
 * Example 2: Static function. The values are retrieved when form is loaded.
 * Example 3: Parametrized query/function.

Parser functions can be parametrized in the same way. In this example, we list all users in the selected group of Group field.
 * Example 4: rmdiv.

In this example, the Endpoint field depends on P2Protocols4 field in study template. The current template is also a multiple template. Endpoint's value is reloaded after P2Protocols4 changes. After reloading, Endpoint may not have any selected values and it is left in an invalid state. In this case, we may want to automatically remove the current instance. This is what rmdir parameter is for.

Download instructions
binary release

Requirement
To install this extension, add the following to LocalSettings.php:
 * Semantic Forms

Demonstration
Demonstration pages can be set up easily locally. First, download demopages.tgz. Upload all the pages in that archive to your MediaWiki using a wikibot. These pages requires SemanticMediaWiki, SemanticForms, SemanticInternalObject and this extension. That archive contains 5 Project. Each Project has a set of Protocols. Each Protocol has two Endpoints as internal object. Then you go to the forms directly to play with the features

Acknowledge
This project is sponsored by BioTeam