In the new OPT, I've redesigned the component design from scratch. It is much more flexible now and allows to make easily many interesting effects. The base rules are still the same, but the rest has changed. This is a sample code showing, how the component-based work with the forms is going to look like:
<opt:snippet name="componentView">
<com:div class="field" invalid="field error">
<p>{$opt.component.title}: <opt:display /></p>
<p class="desc" opt:if="$opt.component.description">{$opt.component.description}</p>
<opt:onEvent name="error" message="info">
<p class="error">{@info}</p>
</opt:onEvent>
</com:div>
</opt:snippet>
<div class="form">
<form method="post" action="skrypt.php">
<opt:input name="name" template="componentView">
<opt:set name="title" str:value="Enter your name" />
<opt:set name="description" str:value="At least 3 letters" />
</opt:input>
<opt:input name="surname" template="componentView">
<opt:set name="title" str:value="Enter your surname" />
<opt:set name="description" str:value="At least 3 letters" />
</opt:input>
<opt:input name="age" template="componentView">
<opt:set name="title" str:value="Enter your age" />
<opt:set name="description" str:value="Scope: 10-99 years" />
</opt:input>
<div class="foot"><input type="submit" value="Send" /></div>
</form>
</div>
The new implementation makes use of the opt:snippet instruction and template inheritance. If you had enough time, you might code the component objects, so that the field titles and descriptions will be unnecessary in the template. A component can handle events, displaying itself and its neighbourhood, managing parameters and tag attributes (we use the com namespace for it). OPT contains only the component mechanism, and the components itself must be written by the end user. The reason is very simple. In order to make a useful component, we should integrate it with the input validation classes, language system, error management etc. The demands are much bigger than OPT is able and is supposed to provide. However, there will be a ready-to-use component implementation: Open Power Forms library.
Unfortunately for the English manual is not started yet. Even the Polish users must use a partially-complete text, without formatting, because the new rendering system is not ready. However, we'll do everything to translate all the text together with some other materials (advices, FAQ, maybe even a tutorial?) into English, before the first final release is done. There is a team, I'll try also to ask some friends and we'll make a serious English support. Just be patient.