Input
The Input component is used to capture user-entered values on a Lowgile screen.
Typical use cases include text fields, numbers, descriptions, quantities, and comments.
- Path: Components → CORE → Input
When to use inputs
Section titled “When to use inputs”Use the Input component when you need to:
- Capture user-entered text or numbers,
- Allow editing of data in a form, and
- Bind values to a screen variable or data object.
Create an input
Section titled “Create an input”In the Lowgile screen editor:
- Navigate to the CORE section of the Components toolbar.
- Drag the Input component onto the screen.
- Position it where the value should be captured.
- Add the relevant properties.
- Bind it to a variable or data object.
Insight
Inputs are typically used inside forms or grouped within layout components such as cards or grids.
Input configuration tabs
Section titled “Input configuration tabs”When configuring an input, you will work across four tabs:
| Tab | Purpose |
|---|---|
| Properties | Defines label, value binding, and basic behavior. |
| Appearance | Controls visual presentation such as placeholder text. |
| Styles | Controls layout, spacing, and alignment. |
| Events | Handles input-related events such as change or focus. |
Data binding
Section titled “Data binding”An input must be bound to a value so Lowgile knows where to store the user’s input.
Typical bindings include:
- Screen variables (e.g.,
screen.comment) - Objects passed into the screen (e.g.,
request.description)
Attention
If an input is not bound to a variable or object, the entered value will not be stored.
Common usage patterns
Section titled “Common usage patterns”The following patterns show how inputs are commonly bound and used in Lowgile screens.
Capture user input
Section titled “Capture user input”Bind the input to a screen variable:
screen.comment
Edit object data
Section titled “Edit object data”Bind directly to an object property:
request.description
Display read-only values
Section titled “Display read-only values”Wrap the input with a Disable component to prevent editing.
Naming conventions
Section titled “Naming conventions”Use clear labels that describe the expected input:
DescriptionQuantityBudget amountComment
Avoid vague labels like Value or Field.
Key Lesson
Inputs define how users provide data. Always bind them correctly and label them clearly to avoid confusion.