Available translations
loading results
Workspaces
Summary: Workspaces are a powerful concept. They enable working on multiple settings in an orderly fashion.
Foundations->Node->Workspace->Definition
A workspace is an entity storing all system and user-generated information, excluding the state and contents of plugins. In technical terms, a workspace is a JSON file.
Foundations->Node->Workspace->Content
A workspace stores information about:
- Any hierarchy that is not included as a plugin.
- Nodes that may be floating around, detached from hierarchies.
- Information regarding the physical position and state of all nodes within the design space, even those detached from hierarchies.
A workspace is not part of any of the hierarchies; instead, it contains them.
Loading Workspaces
Users may manage multiple workspaces, but only one workspace may be loaded in the system at any point.
To load a workspace, click the workspaces tab on the left-hand side of the screen and select one of the available files.
Tip: To load a workspace you got from a third party, you may place the file in the My-Workspaces folder so that you may open it from the workspaces tab. You may also drag the file and drop it on the design space.
Warning: It is not recommended to launch multiple instances of the UI in separate browser tabs to load different workspaces at the same time. The system is not prepared to handle this type of use and it may behave erratically as a consequence.
Saving Workspaces
Any workspace that is saved by the user is a User Workspace.
Note: User workspaces feature a purple background in the workspaces tab.
Workspaces are saved as JSON files in the My-Workspaces folder.
You may save a workspace manually using the following hot-key combination:
Ctrl or Cmd + Shift + Alt + Key-S
Tip: Backing up a workspace downloads the same file to your local Downloads folder. This is a good way to store sequential versions in case you ever need to go back to a previous state of affairs.
A workspace can have the following configuration properties, all are optional
{
"docsLanguage": "EN",
"contributionsBranch": "develop",
"location": "tutorials"
} docsLanuage: sets the language for the documentation
contributionsBranch: sets the git branch for making your contributions
location: a specific folder location for this workspace to live. If you want this to be nested in multiple folders, examples would be copy-trading/live, copy-trading/paper.
Native Workspaces
Superalgos ships with several Native Workspaces. These are pre-configured workspaces built for specific purposes, for example, to host tutorials, demo strategies, specific projects, and so on.
Note: In the workspaces tab, Native Workspaces are marked with the words "Native Workspace", and feature a black background so that you may differentiate them from your own workspaces.
Important: When you load, modify, and save a Native Workspace, the actual plugin file remains intact, that is, the plugin is not modified. Instead, a new file is created in the My-Workspaces folder. This file is a copy of the Native Workspace featuring the modifications you introduced. The copy is saved with the name of the Workspace node, which is usually the same name as the plugin. To save the workspace with a different name, you must change the name of the Workspace node and save.
Creating Workspaces
To create a new workspace, rename any of the existing workspaces by changing the label of the workspace node, and save it as explained above. After you change the label and once the workspace is saved (by any of the usual means), a new file is stored in the My-Workspaces folder.
Tip: The Blank Template Native Workspace is the best to start with if you wish to create your own setup.
Deleting Workspaces
To delete a workspace, delete the corresponding workspace file from within the file system application of your operating system.
Introduction — TOC
You just read page 5 in the topic.
1. Fundamental Superalgos Concepts
3. Hierarchies
4. Workflows
5. Workspaces
6. Nodes and Structures of Nodes
7. References