📄️ AppIDs and window names
In Finsemble, every app has an AppID that is unique for that app type. An instance of an app has a windowName. These values aren't normally exposed to the end user. They are how Finsemble internally addresses each component.
📄️ Workspaces
When Finsemble starts, it automatically re-launches the apps that the user last used, and places them in the same position and with the same state. This is called a workspace. Users can create and save multiple workspaces and easily switch between them.
📄️ Launch groups
You already know that you can use Finsemble workspaces to help your users with their workflows. A company or an assembler can deliver predefined workspace layouts to users b using config. This works well but sometimes a workspace is not enough.
📄️ Using Finsemble APIs
Your Finsemble smart desktop can include diverse types of apps, such as Web, .NET, Java, and so on. You can build these apps with any appropriate framework or API native to their platform. For example, you can use React, Angular, vanilla JavaScript and so on,. on the Web, WPF or WinForms in .NET/.NET core, Swing or JavaFX in Java. In addition, Finsemble provides a number of its own APIs that you can use to build or upgrade apps and services so that they work together, or interoperate, seamlessly in your smart desktop:
🗃️ API tutorials and references
5 items