| Application Component |
A "Finsemblized" application that is visually and logically integrated with your SmartDesktop. |
| Application Management |
Finsemble's suite of functionality that allows end users to search for, sort through, discover, find, and launch their applications. |
| Client API |
A JavaScript API that interfaces with a desktop service through Router messages. Some client APIs are defined for specific desktop service, like the Launcher Client API is specifically for the Launcher desktop service. Other client APIs may provide composite functionality out of one or more existing desktop services, like the Dialog Manager Client API which builds on the Launcher Client. Depending on the desktop service, some parts of the API functionality may be implemented on the client side with the centralized functionality residing on the desktop service side. |
| Component |
A component is a discrete operating piece of Finsemble that lives in an HTML window. A component may have multiple active instances within the Finsemble application, each running in its own Finsemble window (e.g., multiple chart windows, multiple toolbars, etc.). A distinction can be made between UI components, application components, and utility components. |
| Container |
Software, like Electron or NW.js, that allows web technologies to run on the desktop. Finsemble uses Electron as its default container. |
| Desktop Interop |
An integration approach and category of software that involves concurrently running multiple independent applications (web or native), and orchestrating them visually and logically into a single user experience. Finsemble is an example of a "desktop interop framework". |
| Desktop Services |
An active, independently-threaded JavaScript module that provide functionality to components or other desktop services. Desktop services reside in invisible windows; they can be interacted with using a corresponding client API. All communication to and from desktop services is through the Router (itself a desktop service). A desktop service is sometimes simply called a service. |
| Docking |
The ability of a component (like the toolbar) to gain semi-permanent cohesion with something else (like the top of the monitor). |
| Finsemble |
The desktop integration platform is a cooperating set of software components and desktop services used to build SmartDesktops. Based on your business needs, different packages of Finsemble features are available: Workspaces, Connect, Flow, and Native. |
| Finsemble Connect |
Finsemble Connect is designed to integrate your SmartDesktop with your enterprise infrastructure. |
| Finsemble Flow |
Finsemble Flow provides UI capabilities needed to handle large numbers of applications and delivers tools to develop a customized user interface. |
| Finsemble Library |
The Finsemble Library is the entire set of client APIs. These APIs connect to the Finsemble desktop services. |
| Finsemble Native |
Finsemble Native allows you to leverage existing applications written in desktop technologies such as Java or .NET (C#, WPF) with your SmartDesktop. |
| Finsemble Workspaces |
The core Finsemble functionality is contained in Workspaces; it is the base package. |
| FSBL |
The JavaScript object that contains the Finsemble Library. |
| Group |
A collection of windows that are associated in some way, e.g., docked group, a linked group, a composite group. |
| Hotkey |
A button or combination of buttons that invoke a command in Finsemble or an application component, aka a keyboard shortcut. |
| Logical Integration |
Logically integrated components can communicate with each other. Logical integration allows you to create custom workflows. Workflows may be explicit or implicit. Implicit workflows occur automatically, either because the involved applications have been designed to work together, or because they use a shared standard for communication. Explicit workflows occur specifically because Finsemble orchestrates the data exchange between applications. Both implicit and explicit workflows can function alongside one another, giving you resilience when integrating a variety of applications. |
| Module |
An application, component, or service integrated into the SmartDesktop. |
| Quick Components |
A web page that a user visually integrates into Finsemble; a low overhead way to bring a component into Finsemble using only the URL. |
| Router |
A desktop service that is the center point for all Finsemble communication. The Router sends and receives messages between windows, enabling communication between all components and desktop services through three types of messaging: Listen/Transmit, Query/Response, and SubPub. |
| SmartDesktop |
An application made using Finsemble consisting of multiple applications integrated together. |
| UI Component |
A UI component provides basic UI functionality, e.g., HTML windows styled like dialogs and toolbars. |
| Utility Component |
A utility component is a tool whose purpose is configuring or servicing Finsemble, like the Process Monitor or Central Logger. |
| Visual Integration |
All applications launched by Finsemble share an aesthetic. This look and feel is defined by your organization through easy white labeling. Visually integrated windows can snap, dock, group, tile, and tab. Windows launched by Finsemble are persistent between sessions, reloading in the same position and with the same content. |
| White Label |
The ability to edit the style, fonts, colors, etc. of a UI component or the overall SmartDesktop. |
| Window Management |
A suite of functions Finsemble provides to windows that let an end user organize and move windows. Window management functions include hyperfocus and minimize all. |
| Workspace |
A workspace is the highest-level grouping of windows in the Finsemble architecture. A workspace consists of an array of windows and is tracked by a unique name. When the application is reloaded, the workspace is the first thing retrieved from storage. |
Legacy version 5 documentation. View current documentation.