Author: Florian Ledermann (ledermann@ims.tuwien.ac.at)

This is the schema documentation of the APRIL Components sub-schema. For the main APRIL Schema, see the APRIL specification. To get an overview over this schema, you can also use its graphical representation.

Specifiaction and implementation of an APRIL component Wrapper for the interface definition (i.e. field declarations) of the component. A field of the component that can be used for input and output of information. Should be matched by a "in" and a "out" element in each implementation. An input field of the component. Has to be matched by an "in" marker element in the implementation. An output field of the component. Has to be matched by an "out" marker in each implementation. Wrapper for an implementation (of possibly several) of the component. Put your code in here. The type (=host language) of this implementation. At the moment, the only possible value is "OpenInventor" Additional requirements (libraries, files) to run this component. This is a list of space-seperated URLs. The exact meaning of it is language dependent. For OIV components, these are pointers to additional classes that are loaded form external dlls, specified by the syntax path_to_dll/dllName#className (please do not specify the extension .dll, as this is platform dependent) The id of the component. This should be unique. Type used for the implementation A marker for the actual input in the implementation. The exact usage of this is language dependent. For OIV components, this is used instead of the field value of a field that you want to control, and must be empty. A marker for the actual output in the implementation. The exact usage of this is language dependent. For OIV components, this can appear anywhere in your implementation and should contain the full reference name (DEFname.fieldname) of the field that is used for output, and can therefore also contain id markers. Type used for fields, inputs and outputs The fields id/name. This is referenced by the in/out markers in the implementation and in the presentation file. Type of the field. One of the OIV basic types. Default value if no other value is specified. If this is true, the field may be initialized, but not changed afterwards. Only enforced for inputs. NOT IMPLEMENTED. This will be used to read a configuration value from the setup file directly into a component to influence its behaviour independent from the actual presentation. Type used for the in and out markers inside the implementation The id of the field this marker refers to. A marker that will be replaced by a unique id of the instance at APRIL compile time. Use this as a prefix for your internal names to guarantee unique identifiers even if multiple instances of the component are used.