You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 23 Next »

Overview

Displays List provides a data grid, commands, and actions to manage the displays in your solution. It allows users to export displays to a .jpg or the Library and import displays from a file. The interface also allows users to insert, rename, or remove displays from the list and sort the display records by name or date.

Creating a new display in this interface is pretty simple: Click the 'New item' button on the top-left data grid corner to open the 'New Display' popup window. Enter a name for the display, select a Rendering Engine, specify the PanelType, choose a Template and click the 'OK' button to confirm the new display creation.

On this page:


Understanding Displays List

Purpose

The purpose of Display List is to provide a systematic way for users to view and access multiple displays. They support the organization and quick retrieval of different screens, simplifying the process of interface management. This list enables users to add, arrange, and remove displays. The user can also categorize displays, often offering features like sorting and filtering to help users find and select specific interfaces efficiently.

Operation

Display List operates through user interaction, responding to commands to add, delete, or reorder displays. They update dynamically to reflect the current configuration of displays and allow users to maintain an overview of the system's interfaces.

Application

List find use in environments where managing a multitude of displays is necessary. This includes applications with multiple user interfaces, such as dashboard suites, content management systems, and complex software solutions that require navigation between different operational screens.

Usage

Using Display List involves engaging with the configuration interface to manage the application's displays. Go to Displays → List. To manipulate the list of displays, users utilize options like add, rename, remove or sort displays ensuring efficient management of the application's interfaces.


Displays Configuration

Automatic Conversion 

The Portable option allows the automatic conversion between WPF and HTML5 technologies. The user does not need to create two different kinds of screens for Windows and Web clients. Use the Portable option for the rendering engine to create the displays, and will automatically create them in both HTML5 and WPF.  It enables running on the web browser all the displays you created for Windows/WPF.

Display modes

Pages, Popups, and Dialogs are different display modes. They share some similarities, but each has a specific particular or behavior. They are commonly used in application development to build intuitive and dynamic user interfaces.

Page

A Page is a display that always remains open or opens, replacing the previous display, constituting an independent unit of information or functionality within an application. In summary, it is a screen that allows users to perform a specific action, in which access to the page is given from a navigation menu or through other links within the application.

Popup

A Popup is a window that overlays the main application window. It is triggered by an action, like clicking a button or link, or can appear automatically under certain conditions. Its purpose is to provide information or functionality without leaving the current page. It operates independently, with its border, but does not obstruct interaction with the underlying page.

There are two types of popups: modal and non-modal. A modal popup demands interaction before the User can return to the main application, pausing other activities. In contrast, a non-modal popup allows the User to continue interacting with the main application while the popup is open. These popups contain forms, menus, or other components designed to provide access to functions or information for only a short time.

Dialog

A Dialog is a small window that opens on top of all other displays and stays open, blocking the use of other displays until the User closes it. The dialog window appears on top of the main application window and requires user input before dismissal. Typically, it prompts users for confirmation or additional information before proceeding with an action. Dialogs can be modal, meaning the User cannot interact with the main application window until the dialog is closed.

On Resize options

The dropdown menu options specify the settings for resizing an image or element to fit a designated display area.

StretchFill

This option stretches the image to fill the display area, potentially altering its aspect ratio. Distortion can occur if the display area's proportions differ from the image's original aspect ratio.

StretchUniform

This option will scale the image to fit the display area while maintaining its aspect ratio. If the aspect ratios don't match, the image will be scaled until it touches the edges of the container from within, potentially leaving some space in the display area.

Responsive

This option allows the image or element to adjust its size in response to the size of the display area. It's less clear without specific context, but typically, 'responsive' means that the element will scale sensibly to different screen sizes, often maintaining its aspect ratio without distortion.

NoAction

This option displays the image in its original size, regardless of the display area's size, which might lead to cropping or overflow if the image is larger than the display area.


Properties Reference

The Display module has properties enabled as default for each display. These include Name, Engine, PanelType, as well as read-only properties like Preview, BuildStatus, BuildErrors, BuildMessage, and Description.

List properties

The table below provides a reference for the Display List properties:

Display List Properties

ID

A unique identifier for the display.

VersionID

The version identifier, indicating the specific iteration or release of the display.

Name

The name assigned to the display for identification and reference.

Engine

The rendering engine used for the display, such as WPF, HTML5, or both, with the Portable option.

PanelType

The type of panel used, typically Canvas or Dashboard, determining the layout style.

Mode

Read-only. Shows whether the display is used as a Page, a Popup, or as a Dialog. This is defined on Drawing Properties / Display Settings.

Preview

Read-only. Uses the MainPage display as the thumbnail.

Navigate

A function to navigate or link to other displays or elements within the application.

Size

Read-only. The size of the display defined in Draw.

Length

The length property, possibly referring to duration or a specific dimensional measurement.

OnResize

Read-only. Actions taken when the display is resized (Stretch Fill, Stretch Uniform, Responsive or NoAction). This is defined on Drawing Properties / Display Settings.

EditSecurity

Select which Security Permissions group have access to edit this display.

RunSecurity

Select which Security Permissions group have access to this display in runtime.

BuildStatus

Read-only. The current status of the display's build process, such as 'Complete', 'In Progress', etc.

BuildErrors

Read-only. Any errors encountered during the build process of the display.

BuildMessage

Read-only. Messages or notes associated with the build process of the display.

Level

The level or tier of the display, possibly indicating its complexity or hierarchy in the system.

Category

The category assigned to the display, used for classification and organization.

LockState

Read-only. The current lock state of the display, indicating if it's editable or locked for modifications.

LockOwner

Read-only. The user or entity that currently has the display locked, if applicable.

DateCreated

Read-only. The date when the display was initially created.

DateModified

Read-only. The date when the display was last modified.

Description

A brief description or summary of the display's purpose and features.


In this section:

The root page @parent could not be found in space v10.

  • No labels