Panel Layouts are containers that can contain Panels, Panel Navigators, and even other Panel Layout containers. The Panel Layout Properties section allows you to define how the sub-containers inside a panel layout will act. For example, the direction that the containers will flow in, what method of animation will be used to display panels, what buttons reveal hidden panels, and more.

Define the CSS for any locally defined sub-themes. Sub-themes are used to create a custom appearance for certain types such as windows, buttons, tabs, accordions, sliders, switches, etc.

The Web Theme Builder (also referred to as the Stylesheet Builder, Style Builder, or Web Style Builder within Alpha Anywhere) is used to create and modify Web Themes, which are used to style applications in Alpha Anywhere

Define style tweaks, sub-theme, or CSS to augment or override definitions in the web theme.

Determines when the HTML for Panels is computed.

Define the Javascript for any locally defined sub-themes. Sub-themes are used to create custom appearance of certain control types such as windows, buttons, tabs, accordions, sliders. switches, etc.

A Panel Card can be added to component through the 'Panels' menu. Panel cards are useful for defining the different screens, or panels, that a user will see as they navigate through an application on a mobile device. If panel cards are being used inside a component, then every control in that component must be inside a specified panel card. Panel card's come with their own set of properties, listed here:

Open a Page Layout component in a pop-up window, or in a DIV on the current page.

Applies only if the UX Component uses Panels. Specify if the Panel Layout HTML should be computed at design-time, rather than at run time. For a UX Component with a large number of controls, this can mean a significant saving in the time taken to render the component initially. It will, however, take longer to save the component when designing it. If the component uses security groups, or server-side show hide expressions to hide certain controls, then the UX component will need to be recomputed at run-time, regardless of this setting.