Component Appearance

The appearance of a component at runtime depends on a variety of factors, including the type of component, the target platform (web, mobile, Windows, or character mode), the widget, and the properties used to style the user interface.

More specifically, the following factors affect the look and feel of application components:

Platform and operating system.
For web and mobile applications, the OS and web browser can affect the appearance. For example, Windows, Android, and iOs have slightly different user interface conventions, and different browsers may render user interface controls differently.
For desktop applications, the version of Windows can affect the appearance. Character mode applications can run on both Windows and Unix platforms.
Component layout, arrangement of fields, component and field size, choice of widgets, alignment and spacing, and so on.
Type of component. For example, server pages are displayed as HTML in browsers, whereas Form components become windows, and can have associated Menus and Panels. The Dynamic Server Page component offer much more control over application appearance than the Static Server Page.
In desktop applications, the Application Shell (although not itself a component), is visible as an application window, with its own properties and controls.
Widgets. Each component type has its own set of widgets for displaying and modifying data, and each widget has its own set of properties that affect both its behavior and appearance. For more information, see Widgets.
Properties of widgets and other user interface objects (labels, windows, and frames).
Default values for these properties can be specified in the initialization (usys.ini) file, but are overridden when explicitly set in the Uniface IDE or at runtime using script.
In web applications, widget properties can also be set at runtime using JavaScript and styled with Cascading Style Sheets (CSS).
For more information, see Properties for Styling the User Interface.