Compatible with all technologies
Live examples
Input Components Suite How does it work?
Last Updated
11 Mar, 2007

ICSuite is based on runtime DOM instrumentation technique. Once the page is loaded, ICSuite determines the controls to instrument and enhances them. Form controls are usually recognized by "class" or "id" attributes, according to predefined settings.

During the enhancement, ICSuite attaches specific event handlers to the original objects and occasionally modifies DOM.

Why runtime DOM instrumentation?
Such a technique achieves maximum flexibility and compatibility with server-side technologies. It does not really matter what platform, framework or language was used on the server-side, because ICSuite operated the (x)HTML received by a browser. Once this (x)HTML is parsed, ICSuite comes in action and upgrades the chosen HTML controls.

Post-back problem
Another compatibility issue appears on form submission. ICNumeric mask allows any number format including locale specific decimal and thousands separator characters, however server expects a classical number format: no thousands delimiter, a dot as a decimal separator. ICSuite maintains a hidden field with its value formatted according as required by the server.

AJAX/Web2.0 compatibility
AJAX/WEB2.0 applications also take advantage of DOM manipulation without reloading the page. Such manipulation may result in dynamically created form controls: input fields, text areas, etc.. Modern client side scripting standards do not provide a reliable way to be informed of the DOM change. Therefore ICSuite must be explicitly informed of such change in order to instrument newly added elements. See Users Guide ( AJAX/Web 2.0 Integration)

See Integration recommendations, Quick Start and the Users Guide for more details.


InputComponents are trademarks of WiseBlocks. Copyright 2007. All Rights Reserved.