# Overview

**View Editor** is the feature set in SceneComposer for designing and managing <span style="color: rgb(230, 126, 35);">[**View**](https://doc316en.candera.eu/books/view-editor/page/view)</span>s. You can compose screen-level Views by combining Scenes and existing Views, structure their transitions as a tree, and export the result as a Global State Machine asset. In addition, you can visually define event logic and screen transitions for each View as <span style="color: rgb(230, 126, 35);">[**Action Chains**](https://doc316en.candera.eu/books/view-editor/page/action-chain-editor)</span> and reuse them as conditional processing based on input devices and the solution state by using the **ConditionOutputs** defined in ConditionBlocks created in the <span style="color: rgb(230, 126, 35);">[**Condition Editor**](https://doc316en.candera.eu/books/view-editor/page/condition-editor)</span>.

This page provides the View Editor feature set used to work with them. The View Editor consists of the following four panels.

<p class="callout info">For details on Views, see the <span style="color: rgb(230, 126, 35);">[View overview page](https://doc316en.candera.eu/books/view-editor/page/view)</span>.</p>

<table border="1" id="bkmrk-view-definition-edit" style="border-collapse: collapse; width: 100%; height: 257.835px;"><colgroup><col style="width: 24.2208%;"></col><col style="width: 75.8875%;"></col></colgroup><tbody><tr style="height: 80.1136px;"><td style="height: 80.1136px;"><span style="color: rgb(230, 126, 35);">[View Definition Editor](https://doc316en.candera.eu/books/view-editor/page/view-definition-editor)</span></td><td style="height: 80.1136px;">An editor for defining screen-level Views by combining Scenes and existing Views, and for managing screen composition information. Views defined here are referenced as the common screen unit from the **View Tree**, the state machine, and the **Action Chain Editor**.

</td></tr><tr style="height: 80.1136px;"><td style="height: 80.1136px;"><span style="color: rgb(230, 126, 35);">[View Tree](https://doc316en.candera.eu/books/view-editor/page/view-tree)</span></td><td style="height: 80.1136px;">An editor for arranging Views in the solution as a tree and designing screen transitions based on that structure. The structure you configure is exported as a Global State Machine and used as the candidate targets for the <span style="color: rgb(230, 126, 35);">[**JumpToView** Action behavior](https://doc316en.candera.eu/link/582#bkmrk-jump-to-view)</span> configured in the **Action Chain Editor**.

</td></tr><tr style="height: 62.3097px;"><td style="height: 62.3097px;"><span style="color: rgb(230, 126, 35);">[Action Chain Editor](https://doc316en.candera.eu/books/view-editor/page/action-chain-editor)</span></td><td style="height: 62.3097px;">This editor lets you visually define event processing and screen transitions for a View as trigger-based flowcharts. For each View selected in the **View Tree**, you associate an Action Chain and use **ConditionOutputs** created in the **Condition Editor** as branch conditions.

</td></tr><tr style="height: 35.2983px;"><td style="height: 35.2983px;"><span style="color: rgb(230, 126, 35);">[Condition Editor](https://doc316en.candera.eu/books/view-editor/page/condition-editor)</span></td><td style="height: 35.2983px;">The Condition Editor is an editor for visually defining conditions that are evaluated in Action Chains or assigned to the Condition properties of behaviors/Fusion as **ConditionOutputs** inside ConditionBlocks. The created ConditionOutputs can be reused as branch conditions in the Action Chain Editor and referenced from multiple locations in the solution as shared conditional logic.

</td></tr></tbody></table>

Used together, these let you define View-based screen composition and transition logic in a consistent, unified way.