OPTv2: Component template interaction

[whumble]

At last I reached OPT components.
I've read the manual and the gallery tutorial, but...
Could you please give a short overview of
how a component works inside, what interface functions are called first
and why, what happens then.
For example, when processEvent function is called.
I'm browsing through the sources, but am afraid of losing something.
Brief would be great, thanks!

[Zyx]

The order is:

1. __construct() - in your script or in the template, depending on the deployment model.
2. setView() - when the view is deployed in the template.

Next calls are situation-dependent, and you are guarranteed that the first two methods have already been called:

1. display() is called for opt:display tag
2. processEvent() is called for opt:on-event / opt:onEvent tag
3. get() etc. are called for the special variable call $system.component.xyz
4. manageAttribtes() is called for opt:component-attributes attribute.

In OPT 2.1 components support data formats, so you will be able to develop your own component interface and install it in OPT as well.