The Actions view provides a display of all of the available actions that are in context for the given selection in the editor.

Actions can be added through the right click menu in the editor, Add > Action… or in the Actions view directly.

The content of the action list can be sorted by selecting the action table title. When actions are sorted by their triggering event the order in which they appear will also correspond to the order in which they will be evaluated within the same context. If two actions are bound to a gre.press event on the same control, for example a Data Change and then a Screen Fade, then the first action in the list will be executed (Data Change) before the next action (Screen Fade). The order of these events can be adjusted by right clicking on the event and selecting Move Up or Move Down as appropriate.

The content of the action list is automatically populated based on the Designer model object selected in either the editor or in the Application Model view. The content of the list can be filtered in several ways:

The triggering event, action type and context can all be edited inline in the action table. Each action also has its own set of parameters or configuration options. These values can be changed in the lower display area of the Action view once an action selection is made. When the action types are changed, as many argument values from the original action will be migrated to the new action as long as the argument names and types match.

The Application Model view displays a tree representation of the model objects that make up the Storyboard application.

The tree representation aligns with the Storyboard model representation and allows editing operations to be performed on elements that may not necessarily be visible within the editor.

For each of the application, screen, layer and control objects the Application Model can also be configured to display the Actions and Data Variables associated with that model object by toggling the selection in the view's drop down menu.

The visibility of the layer instances and controls can be quickly adjusted through the Application Model view by toggling the setting in the visibility column. The changes made here will be immediately reflected in the editor and will also be reflected in the Storyboard Engine runtime file as the initial setting for the layer instance or control.

Since layers are displayed as layer instances, the tree will show layer and control content several times in the tree. If the Link with Editor toolbar option is enabled, when a model object is selected in the Application Model view the editor will automatically scroll to present the appropriate context of their selection. The same behaviour can be achieved by double clicking on a model object if the view's content is not synchronized with the editor.

The Application Model view tree also displays all of the unused layers and animations that are currently a part of the application design. These model objects can also be manipulated through the Layer view and Animations view respectively.

The Animations view provides an editing environment for creating the animation blocks that are used by the Animation action.

Animations provide a re-usable behaviour for moving a numeric value from one setting to another over a prescribed time frame. The design of animations in Storyboard is such that an animation is created as a generic operation that changes a data value over a period of time through a transformation function. When that animation is executed, it is done so as part of the animation action and as such has an execution context that includes the current screen and the currently focused control.

For example a layer fade animation might be defined as operating on the layer alpha value, using ${layer:grd_alpha}, and changing the value from opaque (255) to transparent (0) over a period of time. Once created this fade animation can then be generically applied to whatever layer is in context when the animation action is invoked.

The Font Styles view is not automatically included in the default Storyboard perspective, but can be included by selecting it from the selecting Window > Show View from the main menu.

The Font Styles view displays the currently defined font styles for the application.  A font style is a combination of font colour, size and other attribute information and can be used to more quickly configure text styles used within the application.

While Designer provides an editing environment that groups the font name, size and colour together, the Storyboard Engine runtime environment considers each of these to be separate properties that can individually be assigned values. To provide a common theme throughout the application interface, it is suggested that common font values be assigned to application global variables that can be easily adjusted to adapt to different language or presentation requirements.

The Images view provides a thumbnail presentation of those images that are currently included in the application design.

The content for the Images view is automatically pulled from the image file content contained in the images directory of the Storyboard project, new content that is imported into this directory in the filesystem will, upon a workspace refresh, be automatically shown in the Images view. Supported image file formats include PNG, JPG, GIF and BMP files. In order to import Photoshop PSD file content, the images must be imported using the File > Import > Photoshop PSD File wizard.

Images can be drag and dropped from the Images view directly into an application design. By default a new control will be created that matches the images size and whose image source is a static value pointing at the dragged out image.

Within the Images view it is also possible to quickly switch an image that used in one context to another using the Swap Image With... right click menu. For example if a number of controls were using an image as a button background and a new image was available that provided an updated look, then after importing the new image one could select the existing image and choose Swap Image With... to quickly change all instances within the application to the new look.

As an application evolves, it will often accumulate a number of unreferenced or duplicate resources. The Image view offers a few utilties to help manage these images.

The Layers view provides a thumbnailed display of the layers used by the currently selected screen and also displays a thumbnail of all of the other layers that are available for use but are not bound to the currently selected screen.

Layers are categorized as either being included on the current screen or not. Layers can be added or removed from the current screen by dragging and dropping them either into or out of the current screen area, or by using the delete key.

Layers are listed according to their front (top) to back (bottom) order z-order presentation. This order can be manipulated by dragging and dropping the layers within the view or using the toolbar buttons. In addition the Layer view provides the ability to change the visibility within the application. If the visibility or z-order are changed, the change is immediately reflected in the editor and will also be reflected in the Storyboard Engine runtime deployment.

Using the toolbar controls in the Layers view it is possible to create new layers and also to open up the Layer editor mode to work with layers independent of the screens with which they are associated.

The Navigator view is a standard filesystem style explorer limited to showing only content available in the Storyboard workspace.

The Navigator view only displays content that has been imported into the workspace and starts with the top level Storyboard Project directories that have been created. Since the workspace allows multiple Storyboard projects to be shown, it is possible to work on multiple projects concurrently all within the same workspace with multiple editors open targeting different Storyboard project. Content and resources can be copied and pasted among different the different editors.

The Navigator view provides a variety of filters to hide/show different file types as well as the ability to group projects together as 'working sets' and then to only display the content from those working sets. For more details on configuring the Navigator and filtering workspace content refer to the Eclipse help Help > Help Contents > Workbench User Guide.

The Outline view provides an overview of the entire editor. The outline content will change to reflect an outline of the editor that currently has focus. Within the Designer environment there are two Outline's of interest, the Storyboard editor outline and the Lua editor outline.

The Storyboard editor outline displays a scaled visual presentation of the entire contents of the editor. If the editor is in Application mode then all of the screens of the application will be shown, if it is in Layer mode then all of the layers will be shown and similarly for the other editor modes. By moving the highlighted area within the Outline view it is possible to change the viewport of the current editor.

The Lua script editor outline displays a listing of all of the identified functions in the file and supports the quick navigation to those functions by double clicking on the function name.

The Problems view shows a list of all problem markers that are created within the workspace. Storyboard provides a project analysis mode that runs in the background to examine Storyboard models and report on design concerns. To enable or disable this analysis mode you can change the Storyboard workspace preference setting in Windows > Preferences > Storyboard > Enable Background Storyboard Project Analyzers.

When the Storyboard Project Analyzers are enabled then as workspace resources change the model will be scanned and analyzed and discovered issues will be reported into the Problems View. Issues that are scanned and reported include:

The Properties view displays information about the current selection in the editor and also provides the ability to change and adjust the properties of that selection. The Properties view is the primary editing location for fine tuning the visual presentation and adjusting data bindings of the application.

For each model element, application, screens, layers and controls, there is a different property interface that provides access to those items that are most relevant to the selected context. The following is a non-exhaustive list of some of the property pages.

On some selections, notably the application, screen, layer and control model elements, the properties view will also contains a Notes tab that allows arbitrary text information to be added to the design model. This information is maintained in the model and is exported within the application design notes.

The Templates view provides users with a list of templates that are available for use in this project. The list of available templates is generated automatically from the contents of the project's templates directory.

When a template is selected its description along with a graphical preview of the template will be shown if they are available. To create a new model object (control, layer, screen etc) that is based template, select one of the template items and drag and drop it into your application.

Not all templates create new Storyboard model objects. Some templates simply enhance the functionality of an existing object and when this is the case, when a model object is selected you can right click on the object and select Templates Apply to access a list of available templates.

For more information about creating templates, see the document section entitled Working With Templates.

The Variables view is similar to the Actions view in that it displays all of the data variables that are in the context of the current selection.

Once a variable is defined and associated with a particular model object context (application, screen, layer or control) then the variable can be referenced as a parameter for actions and render extensions.

There are two different types of data variables that can be defined. A normal variable contains a name, a type (ie number, string) and the value matching the type that should be used when the variable is referenced. To facilitate working with repetitive data within a table control, a special type of variable called a table cell variable can be created. This variable contains all of the same attributes as a normal variable, but is extended to contain an additional row and column information that can be used to specialize a particular value at a given table row and column.

The content of the variable list can be sorted by selecting the appropriate variable table title and the variable values can be edited inline in the variable list by double clicking on the appropriate field that you wish to change.

The content of the variable list, similar to the action list, is automatically populated based on the Designer model object selected in either the editor or in the Application Model view. The content of the list can be filtered in several ways:

Variable Creation

New variables can be created from within the Variables view or at other points within Storyboard Designer. In all cases the variable creation will open New Variable wizard. From within this dialog you can select the name of the variable, its data type and the value to associate with the variable. From this dialog it is also possible to create table cell variables that span a particular row/column range

By default the variable will be created and associated with the current application, screen, layer or control that was selected when the New Variable wizard is launched. However this association can be changed on the second (optional) page of the New Variable wizard where the variable can be explicitly assigned to a different model object.

Note

The type of a variable is important for the Actions or Render Extensions that may use them. If a variable is mis-typed, for example a string variable is created but referenced in a location expecting an RGB color value, then the results are undefined. In general it is a better idea to create variables from the Actions or Render Extensions that will be using them to ensure the proper typing occurs.