29 | | * User interactions are with higher priority than timeline-triggered events. |
| 29 | * For each group in the page, a channel is created. It can contain only this group in its timeline entries. |
| 30 | * The user can drag an audio resource to an area below the group channels. Other events can be drawn here as well. |
| 31 | * User interactions are with higher priority than timeline-triggered events. If a user triggers a link, it is executed no matter whether it conflicts with the actions in the timeline. |
| 32 | * Timelines play automatically but the user can pause them or change the position of the head: |
| 33 | * When a page is shown, its intro is played, followed by the main part. |
| 34 | * If the main part is not looped, the outro is shown after it and the next page is shown. |
| 35 | * If the main part is looped, the outro is shown when the user requests a page change. |
| 36 | * Links cannot trigger timelines. The opposite is possible (and is critical to the correct behaviour of timelines). |
| 37 | * Timelines will be pro-objects. |