Gifs starting to implement

2020-12-15 17:10:48 +01:00
1 parent 4d7dbfd89e
commit bfd340437f
@@ -121,6 +121,7 @@
        <li class="menu-item" onClick="window.contextMenu.toJavascript()">JS Code Style</li>
        <li class="menu-item" onClick="window.contextMenu.toJson()">JSON Code Style</li>
        <li class="menu-item" onClick="window.contextMenu.toTable()">Table Style</li>
+        <li class="menu-item" onClick="window.contextMenu.toGif()">Gif Style</li>
    </ul>

 </body>
@@ -11,8 +11,8 @@
            "text": "Most bots consume data other bots have produced. Because bots need the data as input for their calculations, processes establish a data dependency with the dataset definitions of other bots. The reference provides the process with all the information needed to decode the dataset, enabling it to perform the required calculations."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/indicators-process-dependencies-02.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/indicators-process-dependencies-02.gif"
        },
        {
            "style": "Text",
@@ -11,8 +11,8 @@
            "text": "The execution finished event is responsible for triggering the execution of every process that depends on the data a bot produces. If bot Alice depends on bot Bob, Alice listens to the execution finished event of Bob so that it may start a new execution cycle as soon as Bob finishes its cycle. Alice listens to Bob's execution finished event by establishing a reference from its execution started event."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/indicators-process-execution-started-finished-events-01.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/indicators-process-execution-started-finished-events-01.gif"
        },
        {
            "style": "Text",
@@ -23,8 +23,8 @@
            "text": "To illustrate how fees affect your bottom line, take a look at the image below."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/trading-simulation-fees-fails.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/trading-simulation-fees-fails.gif"
        },
        {
            "style": "Text",
@@ -15,8 +15,8 @@
            "text": "An example of other entities that may be listening to such events is that of plotters. Plotters read datasets and create graphical representations of this data over the charts. Charts are constantly updating the information in the form of candles and indicators in realtime, synchronized with the data being extracted from the exchange by the sensor bot. That kind of automatism is possible thanks to the events that processes trigger every time an execution cycle is finished, signaling to everyone listening that new data is available on each of the impacted datasets."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/indicators-process-output-01.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/indicators-process-output-01.gif"
        },
        {
            "style": "Text",
@@ -11,16 +11,16 @@
            "text": "A single plotter may have several modules. Different modules may be used to plot each product of the bot, or as best suits the expected use-pattern."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/plotter-module-01.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/plotter-module-01.gif"
        },
        {
            "style": "Important",
            "text": "For a bot to use a plotter, the corresponding product definition must establish a reference with the plotter module built to interpret the dataset."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/plotter-module-02-product-link.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/plotter-module-02-product-link.gif"
        },
        {
            "style": "Title",
@@ -11,8 +11,8 @@
            "text": "Vertices are the main element defining polygons. Once created, each vertex must establish a reference to the corresponding point in the charts point."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/vertex-01-add-and-link.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/vertex-01-add-and-link.gif"
        },
        {
            "style": "Text",
@@ -63,8 +63,8 @@
            "text": " isCalculated determines if the field is stored in the dataset or if, instead, is calculated at a later stage. A value true* means that the record is not stored. In the case isCaculated is not defined in the configuration, it is assumed to be false."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/indicators-record-definitions-01.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/indicators-record-definitions-01.gif"
        },
        {
            "style": "Text",
@@ -11,8 +11,8 @@
            "text": "A plotter recursively renders graphics for each period or candle. This means that a definition of what shapes need to be drawn for a single period is required. The plotter does the same thing for every period or candle that is visible on the screen at any point in time, for any time frame, as long as the corresponding data is available."
        },
        {
-            "style": "Text",
-            "text": "<img src=\"Projects/Superalgos/Docs-Gifs/shapes-01-show-off.gif\"></img>"
+            "style": "Gif",
+            "text": "Projects/Superalgos/Docs-Gifs/shapes-01-show-off.gif"
        },
        {
            "style": "Text",