QuickDEV
  • ▶️Quick start
    • 🔃Overview
    • 🔑Security
  • 🎭Users management
    • 👨‍👩‍👦‍👦Members and groups
    • 🔐Permission for resources
  • 🖥️Applications
    • ➕Create applications
      • ⤴️Create application/module
      • 🔲Module
      • ✅Version and Release Management
    • 🎨Application editor
      • 👁️‍🗨️Visual components
        • ⚙️Common component settings
        • ⬆️File upload
        • 📊Charts and graphs
        • 🌄Image
        • 📋Option lists
        • 📑List view
        • ⬜Drawer
        • 🗺️Google maps
        • 📩Messages / Toast
        • 📅Calendar
        • Custom component
      • #️⃣Use markdown
      • ⌨️Keyboard shortcuts
    • 🔗Navigation
    • ⏯️Actions editor
      • ⏱️Date handling
      • 🟰Data selection & JavaScript
      • ⚡Event handlers
      • 🔎JavaScript Query
      • ✖️Dynamic variable
      • 💱Transformers
      • 🧮Data responder
      • ↕️Built-in JS functions
      • 📚Third-party libraries
    • 🖌️Styling
      • 📝Themes
      • 🖍️Customize styles
  • 🚀Database & API
    • 🔎Queries
    • 🧰Query repository
    • 📡Datasources
      • 🌎API
        • 1️REST API
        • 2️GraphQL
        • 3️Google Sheets
      • 🟠SQL Databases
        • 1️Oracle
        • 2️Microsoft SQL Server
        • 3️MySQL
        • 4️PostgreSQL
        • 5️MariaDB
      • 🟡NoSQL Databases
        • 1️MongoDB
        • 2️CouchDB
        • 3️DynamoDB
      • 🔴REDIS
      • 🟢BigData & OLAP
        • 1️Big Query
        • 2️Snowflake
        • 3️ClickHouse
        • 4️Elasticsearch
      • 🌐WebSocket
  • 💻Integrations
    • 1️ANGULAR
    • 2️HTML Pages
Powered by GitBook
On this page
  • Component name
  • Label
  • Tooltip
  • Internationalization
  • Layout
  • Disable & hide
  • Disable components
  • Hide components
  • Vertical space of hidden Components
  • Event handlers
  • User interaction event types
  • Actions for events
  • Order of event actions
  • Style
  1. Applications
  2. Application editor
  3. Visual components

Common component settings

PreviousVisual componentsNextFile upload

Last updated 1 year ago

The visual components in QuickDEV share some general settings and configurations. However, you may encounter components for which certain settings do not apply, and therefore they are not displayed in the Application Editor.

Component name

The component name is crucial, as it serves as the identifier to address a visual component via JavaScript or in any dynamic manner.

Label

Many components offer the option to display labels for users, providing clear communication about the purpose of elements such as input fields.

Tooltip

Internationalization

QuickDEV enables on-the-fly translation of text based on the language information of the user's browser.

Labels and tooltips can use Handlebar JavaScript ({{ }}) expressions to retrieve translations from a JSON registry.

// reading the User Language from Browser 
{{navigator.language || navigator.userLanguage}}
{
    "other_field": [{
        "en-US": "Field"
    }, {
        "de-DE": "Feld"
    }, {
        "fr-FR": "Champ"
    }],
    "other_label": [{
        "en-US": "Label"
    }, {
        "de-DE": "Bezeichnung"
    }, {
        "fr-FR": "Étiquette"
    }]
}

Layout

In the Layout Settings section, you'll find various settings tailored to the selected Component. Typically, these settings pertain to the positioning of the Component.

  • Orientation (left center right justify) (where applicable)

  • Vertical space (fixed, automatic) (where applicable)

  • Prefix and Suffix Icons (where applicable)

Disable & hide

Handlebar JavaScript ({{ }}) expressions can dynamically hide or disable most Components.

Disable components

Hide components

Almost every Component has the capability to be dynamically hidden and shown. This functionality proves valuable for seamlessly switching between Application elements based on user input or interaction.

Vertical space of hidden Components

When components are buried, they do not take up vertical space. While this feature offers a unique potential, it also poses a minor challenge in the Application Editor. However, one advantage is that different Components can be dynamically switched (shown or hidden), allowing for dynamic reactions to user inputs and interactions.

When a Component is hidden, a 'small closed eye icon' appears in the App Editor to indicate its hidden state. However, the component remains draggable and selectable. When selected, it displays its true height until deselected.

Placing other components in the same vertical position as the hidden Component is now possible. However, this may pose a slight challenge in the App Editor when dragging and placing Components that overlap. To address this, it's recommended to utilize a static true/false setting for the 'Hidden' attribute. This ensures that the desired Component is displayed with its height when needed.

Event handlers

Event handlers are one of the powerful concepts of QuickDEV. Nearly every Component can generate events based on user interactions, allowing you to respond with various actions.

User interaction event types

  • Change

  • Focus

  • Blu

  • Submit

  • Click

  • Open / Close

  • Switch Tab

When a Component supports user interaction events, you can define one or multiple actions for a single event type or for different event types.

Actions for events

Each event handler offers a selection of actions from a list of possible options, with each action having its own individual settings.

  • Run Query

  • Control Component

  • Run Javascript

  • Define Dynamic variable

  • Go to App

  • Show Notification

  • Go to URL

  • Copy to Clipboard

  • Export Data

Order of event actions

In a future release of QuickDEV, we aim to enable the ability to rearrange the order of Event Handlers. Currently, this functionality is not available, requiring careful planning of the Event Actions' order if your application requires multiple Event Handlers for a single Component.

Style

Components offer a range of styling options, including color schemes, borders, and background customization.

It's advisable to generally choose between for naming conventions. Kebab case is not recommended, as the "-" between words can potentially be misinterpreted as a minus operation in JavaScript in certain edge cases.

🖥️
🎨
👁️‍🗨️
⚙️
Snake- and Camel-Case
Further details on Event Handlers can be found here.
Click on any Component opens the Properties panel to show all Settings & Configurations.
Make sure you give every component a self-speaking name
The component name is a selector for example in ui based Event handlers
Also in Javascript you use the same name to address the Object, its Attributes and Functions.
Labels helps the users of Apps to understand interaction.
Labels can have different orientations.
Labels can be oriented left or top of a component. The text itself can additionally be oriented left-side or right side.
Additionally it can be helpful for users to use Tooltips for descriptions and suggestions.
Get the User-Language from the Browser
Use a Translation Register as JSON
Many components can set in "disabled" State to not hide Components - but indicate that User cannot enter Data right now.
Components can get hidden by static or dynamic Setting
Hidden Components does not consume vertical space, but can get selected.
As soon as selected or dragged, a Component shows it height.
Components that are hidden can pe placed vertically at the same position.
For each components a set of possible User interaction Events is accessible
Each Component which supports Events can have multiple Handlers (Actions) for Event Types.
Different Components have different support for styleable Attributes.