Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

This page is for application designers who want to design re-usable components and add them to palettes.

Overview

The easiest way to design a screen for an application is to:

  1. Create a dashboard; see Screen Reference Information
  2. Drag in pre-designed components and layouts from the palette. For information about

...

Insert excerpt
_Banners
_Banners
namescreen
nopaneltrue

Overview

You can add your own components to the palettes provided by Phixflow. Alternatively, you can keep your custom components on your own palettes; see Changing or Creating a Palette.

If you have a specific component that you want to reuse on multiple

...

screens:

  1. Convert it to a template component, described below.
  2. Add it to a new or existing palette.

For the repository sections Components and Layout Templates, there is no context menu option to add a new one. 

Making a

...

Template

  1. On a

...

  1. screen canvas, add components from a palette and change their properties to create

...

  1. the layout and design you want.
  2. Set all the style options you require

...

  1. . We recommend that you use shared styles when designing a layout that you want to add to a palette.
  2. Right-click the outermost component for the layout and select 
    Insert excerpt
    _repository_find
    _repository_find
    nopaneltrue
    .
  3. In the repository, right-click the component name.
  4. From the

...

  1. popup menu, select Copy as a Template.
  2. PhixFlow opens a new property

...

  1. pane. This is a copy of the original component, with the Advanced → Template property ticked. It is saved in the

...

  1. Template section of the repository. 
  2. Edit the name to reflect that this component is now a

...

  1. template.

We recommend that you add a layout template to a Using and Creating Palettes:

  1. Open the repository and palette. Drag one of the tabs into the workspace to show the tabs side-by-side.
  2. Drag the layout template from the repository into the palette.

Reusing Components in Dashboards

To use a layout template, simply drag it into the dashboard canvas:

  • either from the repository Layout Template 
  • or from the palette.

When you drag in the layout template, PhixFlow prompts you to add a name. PhixFlow saves the copy in your application as a component on the dashboard, using the new name. This means that changing a layout template

  • does not change the components that have already been copied from it. 
  • new copies will have the change.
Tip

When you set up a layout template, you might want the option of changing the appearance of components that have been copied from a layout template. To do this, set up a shared style.

  1. Configure the formatting in a style.
  2. Add the style to the layout template's Shared Styles; see Style and Shared Styles and Style Order.

Managing Layout Templates 

...

Adding a Template Component to a Palette

  1. In the repository, find a palette and open its properties.
  2. Drag the palette properties tab into the workspace.
    PhixFlow creates a second panel so that the palette properties are displayed next to the repository.
  3. Expand the repository → Templates section.
  4. Drag template components into:
    • Either the palette properties → Components section
    • Or the palette properties → Palette Groups → open group properties → Components section.

The template now appears in the palette as a reusable component that you can drag onto the screen canvas.

Managing Palettes and Template Components

To successfully move a palette to a different PhixFlow instance, you must include

...

all its templates and styles in the export. Consider adding your

...

styles, templates and associated palette to a package, to ensure they are all included

...

; see Package for how to add items to a package.

...

To export your application, click the Administration menu → 

Insert excerpt
_export
_export
nopaneltrue
 → 
Insert excerpt
_export_config
_export_config
nopaneltrue
; see Export Configuration

...