Developers Tutorial
This commit is contained in:
1 parent
93957bf904
commit
81369387f2
21 files changed
+630
No files matched your search
+38
@@ -0,0 +1,38 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 1,
|
||||
"type": "Tutorial - Intro for Developers",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "This tutorial walks you through the technical aspects of Superalgos so that you may take advantage of the infrastructure in place as efficiently as possible."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "I will cover the following topics:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Architecture: Architectural overview of the system."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Client: How the Client is organized."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Frontend: How the UI works."
|
||||
},
|
||||
{
|
||||
"style": "Link",
|
||||
"text": "->"
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "This is a 3-year-old project that has pivoted a few times to reach its current state of development. It was initially intended for trading bots competitions and is now focused on crypto-trading automation in general. The main technical pivot occurred when we decided to depart from a centralized cloud-based app, to a decentralized network of nodes."
|
||||
}
|
||||
]
|
||||
}
|
||||
+38
@@ -0,0 +1,38 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 2,
|
||||
"type": "Tutorial Topic - System Architecture",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "Superalgos is essentially a Node.js application + a Web App."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The overall idea is that Superalgos runs at users' machines. Advanced users may deploy multiple Superalgos nodes in a LAN and distribute tasks easily. In the current version, these nodes are not ready to be exposed to the Internet. Someday they will, and eventually, they will be able to provide services to other users. These services may include:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Data Products: Pre-calculated indicators or studies."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Backtest Execution: To scale testing capabilities."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Live Trading Execution: Only if trusted entities emerge."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Data Processing Execution: External data processing power."
|
||||
},
|
||||
{
|
||||
"style": "Link",
|
||||
"text": "->"
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 3,
|
||||
"type": "Tutorial Topic - Client",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Client has two main components: The Client and the Task Server. When you run the app, what you are running are the Client. An instance of the Task Server is put to run once a user decides to run a task."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Once the services at the Client are running, the default web browser is called with the URL of the local machine so that it may load the UI and let users interact with the system."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The system holds all of its data and logs in the installation folder. The system does not modify—in any way—anything outside the installation folder. Deleting this folder completely removes Superalgos from the computer."
|
||||
}
|
||||
]
|
||||
}
|
||||
+38
@@ -0,0 +1,38 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 4,
|
||||
"type": "Tutorial Topic - Client",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "Is a collection of servers running on a single Node.js process."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The servers are:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Web Server: Serves all the JS files that form the User Interface to the browser."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Web Sockets Server: Enables the UI to reach the Client via WS."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Events Server: Enables the UI to communicate with the Task Manager Server and all of the Task Servers process instances via events over WS."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Task Manager Server: Manges Task Servers processes based on users commands."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "All of these servers are custom built—in-house—for Superalgos. We prefer to build on top of rock-solid, widely-used, low-level libraries only, like WS, for instance."
|
||||
}
|
||||
]
|
||||
}
|
||||
+38
@@ -0,0 +1,38 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 5,
|
||||
"type": "Tutorial Step - Web Server",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Web Server has two main goals: it serves all the JS files that form the Web App and all the data files to be plotted at the charts to the browser that is running the UI."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The complete list Web Server uses is:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "JS Files: Enables the Web App to run on a browser."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "JSON Data Files: Allows the UI to access data to plot."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Images: Images used on the UI are served from the Web Server."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "JSON Workspaces Files: Allow users to create definitions on different Workspaces."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "JSON Plugin Files: Files that are automatically included on Workspaces for convenience."
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 6,
|
||||
"type": "Tutorial Step - Web Sockets Server",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "This is a simple implementation of a web sockets server. It essentially allows the UI or any of the other services to communicate with the Events Server via WS."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The system does not allow different processes to talk to each other via WS. All they can do is talk to the Events Server to subscribe to events or to emit events."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The Web Socket Server enables this indirect communication mechanism between all processes and the UI running on a single machine, as well as communication between processes running on different machines."
|
||||
}
|
||||
]
|
||||
}
|
||||
+30
@@ -0,0 +1,30 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 7,
|
||||
"type": "Tutorial Step - Events Server",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Events Server provides the communication model between processes and the UI. It essentially allows any entity inside each process to create a system-wide event handler and allow any other entity inside a process (or the UI) to subscribe or emit events at that event handler."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Events-based communication happens between:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "UI and Task Manager: To run and stop Task Server processes."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Task Server and UI: To get online feedback of what is going on at the Task Server, to display relevant status info at the UI."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The communication between the UI and the Web Server is HTTP only."
|
||||
}
|
||||
]
|
||||
}
|
||||
+30
@@ -0,0 +1,30 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 8,
|
||||
"type": "Tutorial Step - Task Manager Server",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Task Manager Server is a simple server to manage the execution of Task Servers Node.js processes. It keeps track of all the instances running at any point in time and allows the UI to decide when to run more instance or stop any of those running."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The Task Manager Server provides the following commands to the UI:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Run Task: Used to run a new task, spawns a Node.js fork process where a Task Server is run."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Stop Task: Sends a fork-process-message to the Task Server instance that needs to stop."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Task Status: Tells the caller if the Task Id provided corresponds to a running task or not."
|
||||
}
|
||||
]
|
||||
}
|
||||
+30
@@ -0,0 +1,30 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 9,
|
||||
"type": "Tutorial Topic - Task Server",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Task Server is a Node.js fork process of Client that receives the definition of the Task that needs to run from the UI ."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The definition includes:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Bot to run: The bot might be a Sensor Bot, an Indicator Bot or a Trading Bot."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Processes to run: Each bot definition may have one or more bot processes."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The UI is where all definitions live. Every time the user runs a task, the UI collects all the relevant information into a single, giant JSON object and sends this to the Task Manager Server, which in turn, after the fork process is running, passes this definition to the Task Server instance just created. With that definition, the Task Server knows all the details of the task to run."
|
||||
}
|
||||
]
|
||||
}
|
||||
+34
@@ -0,0 +1,34 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 10,
|
||||
"type": "Tutorial Topic - Frontend",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Frontend is essentially a Javascript web-app running on the browser."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "As of today it contains:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Canvas App: Most of the functionality is here. The name reflects the fact that most of the UI is rendered in an HTML 5 canvas object."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Files Component Includes the mechanisms to read data files in a way that is suitable for navigating through large datasets while plotting the information in real-time."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The UI was built entirely in-house. We did not reuse any framework to display the design space or the charts."
|
||||
},
|
||||
{
|
||||
"style": "Important",
|
||||
"text": "The UI is tested in Chrome only."
|
||||
}
|
||||
]
|
||||
}
|
||||
+54
@@ -0,0 +1,54 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 11,
|
||||
"type": "Tutorial Topic - Canvas App",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "Most of the action happens on an HTML 5 Canvas animation. The rest is pure HTML + CSS, nothing else."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The main object of the Canvas App is called canvas. It is essentially a collection of different space objects:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Charting Space: Where charts are displayed,"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Design Space: Where definitions are maintained."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Floating Space: Enables visual scripting."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Side Space: Currently, the workspace selector."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Docs Space: In-app documentation."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Tutorial Space: Enables tutorials like this one."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Panel Space: Where plotter panels live."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Cockpit Space: Currently, the slider ."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Top Space: Currently, the top bar with logo."
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 12,
|
||||
"type": "Tutorial Step - Canvas Animation",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The animation runs a physics() and a draw() function for each space, allowing each of them to have their own physics engine / rules and render themselves as a top-level layer on the UI."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "At each frame, the animation calls the physics() function of each space first and, second, the draw() function. Then, it requests a callback from the browser and starts all over again."
|
||||
},
|
||||
{
|
||||
"style": "Success",
|
||||
"text": "Depending on how many things the user keeps open, both the physics() call or the draw() call may last more or less time. This makes the frames-per-second variable, and a function of the number of things that need to be calculated or rendered on-screen."
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 13,
|
||||
"type": "Tutorial Step - Charting Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "This is where the charts are displayed. It allows users to navigate through multi-dimensional datasets."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The Charting Space has its own object structure that partially matches the definitions set by the user on the Charting Space hierarchy. This means that, whenever the user adds a chart, removes a scale, or changes a configuration of any of the nodes inside the Charting Space hierarchy, the Charting Space senses these changes and adapts its object model, most of the time in real-time, which in turn changes the way that the charts are displayed."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The Charting Space uses the Files Components as its data provider."
|
||||
}
|
||||
]
|
||||
}
|
||||
+26
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 14,
|
||||
"type": "Tutorial Step - Design Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "Manages the core concept of nodes which, when attached to one another, may form vast definitions easily made and maintained by users."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The system features a file called App Schema which has the rules about the existing types of nodes, which nodes may be the child of other nodes, and which may reference other nodes and which. It also defines the menu items of nodes. All these rules are enforced on the Design Space."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "Users may then attach nodes, establish references between nodes, select menu items, and more..."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The Design Space is tightly coupled with the Floating Space."
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 15,
|
||||
"type": "Tutorial Step - Floating Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "This is like the low-level part of the Design Space. It features a physics engine that governs the physical interactions of floating objects."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "At runtime, each node on the Design Space behaves like a molecule featuring three atoms working together: the first one is called Floating Object and belongs to the Floating Space, which controls its position and collision-related physics; the second one is a UiObject which lives at the Design Space and controls the UI of the node, including menu, label, etc.; the third one is a Node that is—essentially—the information contained in that node."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "When you save the Workspace, Floating Objects and UIOBjects are detached from Nodes, and saved as a big JSON object with only its data."
|
||||
}
|
||||
]
|
||||
}
|
||||
+30
@@ -0,0 +1,30 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 16,
|
||||
"type": "Tutorial Step - Side Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "It is the section on the left, accessed by clicking a tab button. As of today, it features a Workspace selector for users to switch between different workspaces."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "On the Side Space users may:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Select an included workspace: The system ships with one or more included workspaces that serve as examples or case studies."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Select one's own workspaces: By renaming any included workspace, the user may create a workspace and switch workspaces using the Side Space."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The Side Space is expected to grow in functionality in the future."
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 17,
|
||||
"type": "Tutorial Step - Docs Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "This is where the documentation web site is loaded. It's an HTML iFrame inside a DIV, animated in and out of the screen."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "There is an ongoing effort to bring the documentation web site into the app. What you can see today is just the first step in that direction."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The current documentation is implemented as a separate repository, hosted by Github Pages."
|
||||
}
|
||||
]
|
||||
}
|
||||
+26
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 18,
|
||||
"type": "Tutorial Step - Tutorial Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "Enables running tutorials. It is not based on the HTML canvas, but on HTML + CSS."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The Tutorial Space is the highest top-tier layer of all the system since its rendered above everything else. It can manipulate other spaces based on the configuration of each tutorial topic and step."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "Not only may tutorials move the user around the UI, but may also take most actions users themselves may take, like, for instance, running tasks of any kind."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "The Tutorial Space is a new addition to the system. For that reason, few tutorials exist today, but we expect this to change in the future."
|
||||
}
|
||||
]
|
||||
}
|
||||
+22
@@ -0,0 +1,22 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 19,
|
||||
"type": "Tutorial Step - Panel Space",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "The Panel Space is where all panels defined by plotters exist. The space has its own physics engine which governs the way users interact with panels, and panels with other panels."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "Panels are constrained within the boundaries of the Panel Space, which matches the boundaries of the Charting Space."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "Although the panel space has existed since the project's inception, it is still quite underdeveloped, and there is a lot of room to improve it."
|
||||
}
|
||||
]
|
||||
}
|
||||
+38
@@ -0,0 +1,38 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 20,
|
||||
"type": "Tutorial Topic - Files Component",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "Encapsulates different data providers able to read datasets organized in different ways."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "The system defines these types of data providers:"
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Market Files: For time-frames of 1 hour and above, it is convenient to have a single file with all the data of the whole market."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Daily Files: For time-frames below 1 hour, up to 1 minute, it is convenient to split market data into one file per day."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Single File: Sometimes a process may generate a single file irrespective of the time-frame."
|
||||
},
|
||||
{
|
||||
"style": "List",
|
||||
"text": "Files Sequence: Some processes may produce a sequence of files."
|
||||
},
|
||||
{
|
||||
"style": "Note",
|
||||
"text": "Daily Files are managed by a File Cursor which dynamically loads the files of one day and its neighboring days."
|
||||
}
|
||||
]
|
||||
}
|
||||
+26
@@ -0,0 +1,26 @@
|
||||
{
|
||||
"tutorial": "Developers Intro",
|
||||
"pageNumber": 21,
|
||||
"type": "Tutorial Topic - Parting Thoughts...",
|
||||
"definition": {
|
||||
"icon": {
|
||||
"project": "Superalgos",
|
||||
"name": ""
|
||||
},
|
||||
"text": "As you can see, Superalgos is much more than a trading bot. It's a holistic infrastructure to manage complexity in the easiest way possible for users."
|
||||
},
|
||||
"paragraphs": [
|
||||
{
|
||||
"style": "Text",
|
||||
"text": "This introduction covered the highest level topics of the system in the hope it may help you understand the foundations on which the system is being built."
|
||||
},
|
||||
{
|
||||
"style": "Callout",
|
||||
"text": "We hope you agree it's a good idea to reuse this infrastructure to build trading intelligence rather than code a trading bot from scratch. We hope more devs will join us!"
|
||||
},
|
||||
{
|
||||
"style": "Success",
|
||||
"text": "If you like the project, there are many ways to contribute. Take a look at this page featuring the roadmap to becoming a part of the team."
|
||||
}
|
||||
]
|
||||
}
|
||||
Reference in new issue
Block a user