A

App

Kelp app is a web application built on the Kelp platform that runs in a browser and provides interactive functionality to its users.

C

Canvas

Canvas is a working space for app building. Place new components on the canvas to create a schema.

Component

A component is the building block in Kelp used to create the app schema. Each component serves its purpose; there are widgets, connectors, utils, data processing components, and many others. Check Components help articles, and the Getting started guide to learn how to use them.

Components Library

Components Library is the list of all Kelp components available. We constantly add new components to the library; remember to check for updates.

Connection

Connections are represented as wires between Kelp components. Connecting components with each other, you make data flow through the application. Connections are divided into regular and query connections. Please refer to Components help articles to get more details on its capabilities.

Connection monitoring

Connection monitoring allows examining wire logs for errors. Refer to Interface overview for instructions.

Core components

Core components are system and service components that are used to build your app logic.

D

Data Gateway

Data Gateway is the mediator between your application and external data sources. When you connect the app to any external source, all the requests and data transfers go through the Data Gateway.

Data Source Connection

Data Source connection is a different type of connection established by adding particular connection components - Protocols and Security - and configuring security credentials for secured connections.

Data Transformations

Data Transformation allows you to convert data if the initial data format cannot be visualized. Mostly data transformation is applied to connection wires, changing the data to widget readable format. Refer to the Data transformations article to learn Kelp transforming capabilities.

Design mode

Design mode allows arranging all app items and components for a better user experience; any widget placed on the canvas in the Design mode is available for users.

Developer Mode

Developer mode allows you to build data apps arranging components and widgets into a schema.

E

Event

An event is an occurrence that takes place in your App and triggers a response from the Kelp environment. You can monitor events on the output ports of each component. There're two options: you can either open the dialog screen on each connection or connect a Log widget to the schema.

G

Group

Components may be organized in groups; use grouping to support multiple levels on the schema, and simplify it. You can include a few components in the group having one objective, or you can group many components if they are related to one piece of the app logic.

L

Layout

The layout is the presentation layer configured in the Design mode; arrange and format widgets, break the app down into pages, set up navigation, and update the style.

P

Ports

Each component has input and/or output ports, one or many. Connections to some ports are optional; it depends on the component's objective and the configuration details.

Preview Mode

Preview mode allows examining the app from the users’ point of view.

Q

Query connection

Some components support a complex interconnection logic; query connections are used when data should be prepared before it is sent to the component input port. Query connections could be established only between compatible components via qPorts. Please refer to Components help articles to get more details on its capabilities.

S

Schema

Schema is the logic layer where you can add your data, transform it, perform calculations, configure widgets and application interactivity. Customize the schema using the Developer mode.

Signal

Kelp environment has a special event type - a signal. A signal is an instruction for a component to react in a certain way. Currently, Kelp supports the following types of signals:

  • SCOPE_CHANGED - signals a partial reset or change of the data. Widgets can reset their state, but will not trigger a full re-rendering.

  • PROGRESS - signals the status of completion for some long-running processes. You can also provide a % of completion. By receiving this signal widgets will activate and display their progress bar.

  • CUSTOM_ERROR - signals an exceptional situation with a predefined HTTP status code (403 Forbidden or 404 Not Found).

  • UNKNOWN_EXCEPTION - signals unexpected exceptional situation. For example, the HTTP component sends this type of signal on its output when an error response is received.

  • BEFORE_LOAD - notifies the component that soon it will get some data. Also, it initiates the progress bar on a widget.

  • AFTER_LOAD - notifies the component that all data is loaded and hides the progress bar on a widget after data is fully loaded. BEFORE_LOAD and AFTER_LOAD usually goes one by one, in case the component/widget received one signal, but didn't receive another, it will not process the data properly.

Use Signal and Inject Signal components to manage signals in your App. Some components, such as HTTP, can issue signals without any intervention from your side. Vega component operates the signal in a different way configuring the chart’s reactions to various events like mousedown or click. You can find more information on how to configure signals on the Vega website.

Stream

A data stream is a conveyor-like sequence of data when each piece is transmitted over time. The component that receives the stream processes each piece at a time. The typical data stream passes a selection of one or multiple entities on a List widget to another component. Each time you update the selection on the widget, a new array of IDs is issued to rewrite the previous one.

T

Transformations

Data Transformation allows you to convert data if the initial data format cannot be visualized. Mostly data transformation is applied to connection wires, changing the data to widget readable format. Refer to the Data transformations article to learn Kelp transforming capabilities.

U

UI blocks

UI Blocks are primitives used to create your custom components.

V

Vega Chart

Vega Chart is an integrated widget provided by Vega & Vega-Light Visualizations grammar to create visualization designs.

W

Widgets

Widgets are visual components added to the layout and visible to App users. Widgets are charts and graphs, icons, tabs, lists, cards, etc. Check Widgets section in Kelp Help for more details.

Wires

Wires represent connections between Kelp components. By connecting components with wires, you make data flow through the application. Please refer to Components help articles to get more details on its capabilities.

Did this answer your question?