A cell that provides a result, that is runs, only in the following cases:
- The user clicks the “play” button on the cell.
- An event binding has a source that is an action cell and the end-user causes the associated event to happen. For example, the end-user clicks a button and as a result causes the action cell to run.
Similar to a real-time cell, but accumulates values over time.
Note: a flow launched from an accumulating cell is never automatically terminated, only when the =STOP() function is invoked from a different cell.
A binding where the source is a vertical group of cells -- the group starts where the user clicked to define the binding and ends at the first blank cell that is detected.
The mirror image of an auto column binding.
A binding where the source is a horizontal group of cells.
The group starts where the user clicked to define the binding and ends at the first blank cell that is detected.
A two-way link between a property on a component and a spreadsheet cell.
A binding always has a source -- the cell or group of cells in the spreadsheet -- and a target -- the component’s property that the source is linked to.
The basic unit of the spreadsheet where two things happen:
- Formulas are entered.
- Cloud flows are invoked and results are returned.
A visual element, such as a Button, Label, Box, or TextInput, that appears on the screen.
Something that occurs when an end-user interacts with a component. Examples of a component event includes clicking a Button, entering text in a TextInput, or moving the mouse pointer over a Box.
A value that defines the appearance or behavior of a component.
All component properties can be bound (via a binding) to a cell or group of cells in the spreadsheet.
A design fully defines how an application will look, feel, and behave. It includes both the behavior that occurs in the browser or on a mobile device, and the behavior that occurs in the cloud.
An authoring environment for the creation of applications.
The expression that is used to create an empty frame :
A person who consumes the resulting applications created by an organization member.
A binding where the source is always exactly one cell, even if the component is repeated itself or is inside of a parent component that is repeated.
A pipeline-like end-to-end scenario, built from flow blocks. Must have one or more input blocks and one output block.
A single element of a flow scenario. For example, the Read Database block gets data from a database and returns it as a frame, when called from a spreadsheet cell.
A flow block has one or more input and output connectors. Can be linked with other flow blocks to build a complete flow.
A block and arrows diagram editor that allows you to visually define logic that runs in the cloud and possibly in the background. Examples include things like “sending an email”, “constantly collecting sensor data”, or more everyday things like “write data to a database,” “read data from a database”, etc.
A combination of mathematical expressions and/or functions.
One of the building blocks of an application. Takes one or more inputs and provides a result.
A two-dimensional data structure organized in rows and columns.
A special function that takes a range and creates a frame as a result.
Also it is possible to use string literals to create a frame object inside a cell.
A formula that allows you to create a frame without referencing a range.
The following is an example of a frame row literal.
The following is an example of a frame column literal:
A binding where more than one property on a component acts as the target of the binding.
When such a binding is defined in the spreadsheet, the columns in the spreadsheet must be adjacent to each other.
A separate window similar to a spreadsheet that is displayed as a result of opening a frame.
A unique URL like my-company.mintdata.com, where all members of your organization can log in to collaborate on the creation of designs.
The site-name part in a URL like site-name.mintdata.com.
A unique place where users log into your organization on the MINTDATA™ platform.
The panel that contains the following sections:
- Pages. Create, rename or delete pages, control overlays.
- Components. Lets you add new components to the page.
- Outline. A view of the hierarchy of all components on the active page.
An overlay is what we call a page when it is overlaid on top of another Page.
This can happen in one of two ways:
- By overlaying one page on another in the Outline panel of the Designer.
- By using the SHOW_OVERLAY() function to cause a page to appear as an overlay.
A distinct set of components that appear on the screen at a given time.
All pages in a design are always of the same size. Resizing one page causes all pages to be of this new size.
With a self-directed layout and this behavior, it’s possible to create applications that look right on mobile phones, tablets, and the desktop web.
A list of pages overlaid on the currently selected page. You can view this list of overlays by clicking on located next to a page's name in the Pages section of the Outline panel. Note that the icon is displayed if the active page has overlays associated with it.
The layout of a component whose position is defined by its parent.
A pinned overlay is an overlay that stays present on the page whenever the page is active. Pinned overlays are not affected by the HIDE_ALL_OVERLAYS() and HIDE_TOPMOST_OVERLAY() functions. This is useful for things like headers and footers.
A mode in the Designer such that an organization member can experience all component event as they would behave in a published application.
There is no other difference in the preview mode. As a result, the only reason to enter into the preview mode is to interact with components on the design.
The panel that allows you to control properties and events of the selected component: modify them, bind to the spreadsheet, or use Repeater.
When a design is published, it becomes a published application.
A published application is then accessible to end-users on the web and on mobile devices.
This is akin to publishing a document, except in this case it’s the publishing of a software application.
A published application can be accessed in one of three modes:
- Public: anyone can access the application, no login is required.
- Anyone With Link: anyone with a unique link can access the application. Similar to “Anyone With Link” functionality found in Google Docs.
- MINTDATA™ Login: only Organization Members from your organization on mintdata.com can access the application. Note: for Enterprise plans where the entire platform runs on-premise, this option is not available.
- Single Sign-on: an account in ADFS, LDAP, or a public identity provider like Google, Facebook, GitHub or Twitter. Note: this option is available on Enterprise plans only.
A cell that contains the results of calling a flow.
Functionality that allows any component to be repeated multiple times on the screen.
The number of times the component is repeated can be:
- A fixed number of times.
- A varied number of times, based on the number of non-blank rows or columns detected in a spreadsheet.
The layout of a component whose position is always relative to the parent but is not defined by the parent.
Just like a regular spreadsheet, a tab that contains a collection of cells.
A logical grouping of designs.
The place where all application logic that happens in the browser or on a mobile device is defined. Consists of a group of sheets which in turn contain cells.
The place where you create and manage the user interface of your application.
Overlays can be either pinned or regular. Pinned overlays become a permanent part of the page that they are attached to. That is, when the page is active, all of the pinned overlays will always appear with that page. This is useful for things like headers and footers.
A place where people log in to collaborate on the creation of designs in the Designer.