Named parameters

Rob

IDEA

The ability to set up named parameters. These could be numeric / text and be used throughout the application. These parameters are then available to be retrieved using the name of the parameter enclosed in braces/curly brackets {parameter_name}.

EXAMPLE

A parameter could be set that defines the button background colour:

Name: button_background_colour

Type: Text

Value: rgba(25, 224, 209, 1)

This could then be used in the following way where instead of defining the colour with rgba(25, 224, 209, 1) the parameter is written enclosed in { }.

Board identifies that there is a parameter {button_background_colour} and substitutes in the stored value rgba(25, 224, 209, 1) functionally giving the result;

BENEFITS

If used throughout a capsule it will mean every button colour can be updated simply by updating the stored value for that named parameter, this could potentially also be expanded to have this set by user so they can customise their view of applications. This could be used in many different places such as text parameters for font style, numeric parameters for font size etc.

CONSIDERATIONS

1. There would need a fallback default colour should the parameter return an invalid value not compatible in the place where it has been substituted.
2. Braces {} were used as an example to enclose the parameter name but Board would need some way to identify where substitutions are required - potentially using the substitution formulas @abc
3. Where are these parameters stored
   1. Database - allows them to be used across different capsules
   2. Capsule - duplicates set up and amendment
   3. Cube - maybe a special cube that can be called on

Conflicts - e.g. stored in database and a screen is set to Multiple data model and each database contains the exact same named parameter