New input components

FirstSpirit Version 4.2 marks the start of fundamental revision and consolidation of FirstSpirit's input component model (cf. "FirstSpirit Roadmap 2009-2012"). Within the scope of these activities, a whole range of input components previously implemented separately will be brought together.

It is planned to bring together the following input component groups:

• Single value input components: Links to other FirstSpirit objects, e.g. CMS_INPUT_FILE, CMS_INPUT_PICTURE, CMS_INPUT_PAGEREF, etc.
• Set-valued input components: CMS_INPUT_CONTENTLIST, CMS_ INPUT_TABLIST, CMS_INPUT_CONTENTAREALIST, CMS_INPUT_LINKLIST

The implementation is in two phases:

• With FirstSpirit Version 4.2, a new generation of input components will be gradually introduced with the name prefix "FS_" instead of "CMS_INPUT_". These new input components will be gradually added within the scope of continued development of FirstSpirit and will be adjusted to clients' needs.
• The new input components cannot be officially released until FirstSpirit Version 5.0. This process is necessary, as release of the components in Version 4.2 would already bindingly specify the parameter assignment and API. This would make flexible further development of the components, taking into account customers' interests, no longer possible.

As the official release will not take place until FirstSpirit Version 5.0, the input components ("FS_") can already be used in FirstSpirit Version 4.2, but in Version 4.2 their status is "under development". In specific terms, this status means:

• The input component is supported within the scope of the usual quality assurance and debugging.
• The persistence format will be kept compatible during the continued development, i.e. once data has been entered, it can continue to be imported. However, there is no downwards compatibility with FirstSpirit Version 4.1.
• The aim is not to make too many changes to the user prompting. However, as especially optimisation of the user prompting, is the objective of the iterative procedure, editorially relevant changes may well occur.
• The aim is to keep the parameter assignment of the input component compatible. Should this not be possible, a corresponding announcement will be made within the scope of the "FirstSpirit Release Notes".
• The API of the input components will change during the course of the development. If possible (and meaningful) the API changes will be compatible. However, incompatible changes are possible and will also be announced within the scope of the "FirstSpirit Release Notes".
• As release of the "FS_" components is not planned until FirstSpirit Version 5.0 with WebEdit 5.0, support for these component in WebEdit 4.2 will be very rudimentary. An exception here is all new input components which are necessary for the migration to generic link editors.

The implications for use in productive projects are: Use of the components is possible, if the project developers dispense with use of the API and they are willing to potentially subsequently adjust the parameter assignment of the input components. The editorial users should be prepared for changes in the user prompting. Should this be unacceptable, use of the new input components should be dispensed with in Version 4.2.