Based on number allow the usage of wildcards symbol (*) to indicates an unbounded number. Legal version number using maximum 3 digits and optional alpha, beta or rc version. Askia Design Control Root node of the ADC definition. Version number of the ADC format definition. (Not the version of the control but the version of the ADC format) Based version of the ADC. Compatibility version with Askia product. Meta-data of the ADC. Unique identifier of the ADC control. Should be share accross version of the same ADC. User friendly name of the ADC. Version of the ADC. This version must contains at least one digit and maximum 3 digits separates with a dot period (ex: 1, 1.0, 1.0.1). It could also contains an extra version information such as 'alpha', 'beta' or 'rc' optionally follow by a number (ex: 1.alpha2, 1.0.beta10, 1.0.1.rc3). Release date of the ADC. List the categories of the ADC. Freeform text which indicates the category of the ADC (ex: Sliders, Flash ...). Describes the ADC. Name of the ADC author(s). Name of the company who provide the ADC. URL to the author/company web site. URL to the help file of the ADC. Default size of the ADC, mostly use for the ADC-Flash. Width of control in pixel. Height of control in pixel. Constraints to indicates the allowed context of the ADC. Define the constraint on a given context such as questions, responses or controls. Indicate the type of the constraint. Use to indicate the constraint on questions, such as the type of allowed questions. Use to indicate the constraint on responses, such as the min and max allowed responses. Use to indicate the constraint on controls, such as the type of allowed controls. Use for the constraint on questions, indicates the if the ADC is allowed on chapter. Use for the constraint on questions, indicates the if the ADC is allowed on single closed questions. Use for the constraint on questions, indicates the if the ADC is allowed on multi-coded question. Use for the constraint on questions, indicates the if the ADC is allowed on numeric questions. Use for the constraint on questions, indicates the if the ADC is allowed on open-ended questions. Use for the constraint on questions, indicates the if the ADC is allowed on date questions. Use for the constraint on questions, indicates the question require a parent loop. Use for the constraint on responses, indicates the minimum of allowed responses. Use for the constraint on responses, indicates the maximum of allowed responses. Use for the constraint on controls, indicates if the ADC is allowed on label controls. Use for the constraint on controls, indicates if the ADC is allowed on text box controls. Use for the constraint on controls, indicates if the ADC is allowed on list box controls (combobox and list). Use for the constraint on controls, indicates if the ADC is allowed on checkbox controls. Use for the constraint on controls, indicates if the ADC is allowed on radio button controls. Use for the constraint on controls, indicates if the ADC is allowed on response block. List all possible ADC's outputs. A condition could be specify for each outputs to make it alternative. Indicates the id of default output to use when none of the output conditions matches. It is require as the latest output fallback. Enforce uniqueness of the output ids. The default output id should match one of the output id. Output of the ADC. Unique identifier of the output. It use on the defaultOutput attribute of the outputs element. Indicates if the system must generate or not the default controls. Only for question(s) inside a loop. Indicates the maximum of iterations that could be handle by the ADC. If a bound value is set: - On the first or middle iterations, the engine will not generate remain merge controls on the page - On the last iteration, the engine will generate the remain merge controls on the page Describes the element AskiaScript condition to use the current element. Content of the specify output. File use to generate the content. Indicates the type of content. According to this type, the system will automatically generate the proper HTML fragment unless the <yield> is specify. Flash content. Will be inserted using <object /> tag. The content must be static or share. CSS content. Will be inserted using <link href /> tag when static or share or using the <style></style> tag when dynamic. HTML content. Will be inserted as it is or interpreted when it's dynamic. Javascript content. Will be inserted using the <script src /> tag when static or share or using <script></script> tag when dynamic. Image content. Will be inserted using the <img src /> tag. The content must be static or share. Video content. Will be inserted using the <video src /> tag. The content must be static or share. Audio content. Will be inserted using the <audio src /> tag. The content must be static or share. Arbitrary binary file. Will be inserted according to the specify <yield> tag. The <yield> should be specified using a binary content otherwize the system will not create an output. Text-based file. Will be inserted as it is or interpreted when it's dynamic. Indicate how the content will be treat and where the system should find the content file. The share content is always associated with a file and must be place in the /Resources/Share/ folder of the ADC. The share content will be extract in the resources folder of the survey /Resources/SurveyName/. This kind of content, could be share accross ADCs and will not be overrides when it already exist in the folder. The static content is always associated with a file and must be place in the /Resources/Static/ folder of the ADC. The static content will be extract in the resources folder of the ADC /Resources/SurveyName/ADCname/. The dynamic content could be file (text based) or in-line code define in the definition of the content. It could embed AskiaScript to execute. When the content is a file, it must be place in the /Resources/Dynamic folder of the ADC. The dynamic content will not be extract but load in memory. Indicates how and where the system must render the current content. The resource will not be rendered. But it's still available through HTTP request. The resource will be inserted in the head section of the HTML document. Mostly use for CSS stylesheet. The resource will be inserted at the position of the ADC control. Mostly use for the HTML injection. The resource will be inserted at the end of the document, just before the end of the closed body tag. Mostly use for javascript insertion. Additional attribute to add or to overwrite in the auto-generated tag. When <yield> is present the attribute is not take in account. Name of the attribute. Value of the attribute. This value could be dynamic, embed AskiaScript code. Dynamic string which indicates how the content must be rendered. It override the built-in HTML render by the system. Must be use for the non-manageed file, such as binary or text List of properties accessible through the user interface. Category of the properties. Unique id of the category. User friendly name of the category to show on the interface. Indicates if the category should be collapsed by default. Enforce uniqueness of the property ids. Property accessible through the user interface. Indicate if the property is visible in the user in Askia interface. Describes the aim of the property. Default value of the property. Indicates the default value for the specified 'theme'. Also see the <globalproperty id="askia-theme" /> Unique id of the property to access on it using the AskiaScript. This id should not be a reserved id. See <globalproperty> User friendly name of the property to show on the interface. Type of the property. Property as string. The string could be validate against a regular expression using the pattern attribute. Property as number. The number could be restricted using the min/max/decimal attribute. Property as boolean. The value must be true or false. Property as color. The format of the color could be specify using the colorFormat attribute. Property as string. Indicate the name of a resource file already register. This file must be on the survey and accessible through the url ../Resources/[Survey name]/ Property as question. Indicate question that could be used in the current ADC. Indicate if the value of the property could or not embed AskiaScript code. The static value is use as it is. The dynamic value will be evaluated before his usage. If the value return by the evaluation doesn't produce an expected value according to the min, max, decimal, pattern, fileExtension... then the default value will be used. Indicate if a value is require for this property. Use with the type string, the regular expression pattern will be use to validate the value entered. Use with the type number. Indicates the minimum allowed value. Use with the type number. Indicate the maximum allowed value. Use with the type number. Indicate the maximum number of decimal digits allowed. Use with the type color. Indicate the format of the color. Color in RGB format (Red, Green, Blue) (RR,GG,BB) Color in RGBA format (Red, Green, Blue, Alpha) (RR,GG,BB,AA) Color in Hexadecimal format (#rrggbb) Use with the type file. Indicate the allowed extension of the file. Default value of the property. Indicates the identifier of global property to use. This identifier implicitly specified the category, name, type, mode... of the property. List all possible themes. Allow properties to multiple default values for each theme. If a <value /> of a property doesn't specify the theme, a theme named 'default' will be automatically associated with it. category: 'General' name: 'Theme' type: 'strubg' description: 'Predefined themes' mode: 'dynamic' Requires: <options> tag Once this global property is present in the config file, it allow user to generate an extra input for the "Don't know" answer. It's specially useful for the non-closed questions such as open-ended, numeric or date. category: 'General' name: 'Add "Don't know" input' type: 'boolean' description: 'Add a "Don't know" input to enforce the answer' value: false mode: 'static' REMARKS: The additional "Don't know" answer could be accessible through the AskiaScript code: ' dim lastResponseIndex = CurrentQuestion.AvailableResponses.Count - 1 ' CurrentQuestion.AvailableResponses[lastResponseIndex] This global property is automatically displayed in the interface when the question is in a loop. It allow user to indicates how many iterations he want to display. The value associated is used in conjunction of the maxIterations attribute of the <output> element. The system will use the minimal value of both. category: 'General' name: 'Max. iterations' type: 'number' description: 'Indicates the maximum number of iterations to display' value: * or 0 mode: 'dynamic' REMARKS: It's not necessary to create this property, the system will automatically create it. Enumerates all allowed values. Allowed choice. Value of the option. User friendly text of the option. Enforce the uniqueness of option value