Superalgos Client refactoring

Platform/UI/EventsServerClient.js

@@ -195,7 +195,7 @@ function newEventsServerClient(networkNode) {
                 if (networkNode !== undefined) {
                     if (networkNode.payload !== undefined) {
                         if (networkNode.payload.uiObject !== undefined) {
-                            networkNode.payload.uiObject.setErrorMessage('Failed to Connect to Superalgos Client via WebSockets. Retrying in 1 minute. Check at this node config if the host property has the IP address of the computer running Superalgos Client.')
+                            networkNode.payload.uiObject.setErrorMessage('Failed to Connect to Superalgos Platform Client via WebSockets. Retrying in 1 minute. Check at this node config if the host property has the IP address of the computer running Superalgos Platform Client.')
                         }
                     }
                 }
@@ -204,7 +204,7 @@ function newEventsServerClient(networkNode) {
             if (networkNode !== undefined) {
                 if (networkNode.payload !== undefined) {
                     if (networkNode.payload.uiObject !== undefined) {
-                        networkNode.payload.uiObject.setStatus('Connected to Superalgos Client via WebSockets.')
+                        networkNode.payload.uiObject.setStatus('Connected to Superalgos Platform Client via WebSockets.')
                         retryCommandsPhysics()
                     }
                 }

PlatformRoot.js

@@ -6,7 +6,7 @@ load all node dependencies and get them ready to the actual App.
 */
 
 /* 
-The CL object is accesible everywhere at the Superalgos Client. 
+The CL object is accesible everywhere at the Superalgos Platform Client. 
 It provides access to all modules built for this Client.
 */
 global.CL = {}

Projects/Foundations/TS/Task-Modules/EventServerClient.js

@@ -49,7 +49,7 @@
             WEB_SOCKETS_CLIENT.onerror = err => {
                 console.log('[ERROR] Task Server -> Event Server Client -> setuptWebSockets -> On connection error -> error = ' + err.stack)
                 console.log('[ERROR] This could mean that the port '+ port +' is taken by some other app running at your system. To resolve this issue, please pick another port number and change it at the .ENV file inside the Superalgos folder AND at the .Environment.js  file inside the TaskServer folder. After that run the app again. ')
-                console.log('[ERROR] If you are debugging, it can also mean that the Superalgos Client is not running. ')
+                console.log('[ERROR] If you are debugging, it can also mean that the Superalgos Platform Client is not running. ')
             }
             WEB_SOCKETS_CLIENT.onopen = () => {
                 try {

README.md

@@ -101,7 +101,7 @@ Before you begin, it is recommended that you set up Chrome/Safari as your defaul
 
 **IMPORTANT:** Use Chrome/Safari so that you have a similar environment as the dev team in case you need help. We are not testing on any other browsers, and it is a well-known fact that browsers behave differently.
 
-# Superalgos Client Installation
+# Superalgos Platform Client Installation
 
 ## 1. Fork the Superalgos Repository
 
@@ -283,7 +283,7 @@ If you're running Superalgos on a headless linux server like a Raspberry Pi, you
 Create a `superalgos.service` file looking like this (change `<user>` to your user name and `/path/to/Superalgos` to your Superalgos folder, for instance `/home/John/Superalgos`):
 ```
 [Unit]
-Description=Superalgos client
+Description=Superalgos Platform Client
 
 [Service]
 Type=simple

TaskServerRoot.js

@@ -6,7 +6,7 @@ load all node dependencies and get them ready to the actual App.
 */
 
 /* 
-The TS object is accesible everywhere at the Superalgos Client. 
+The TS object is accesible everywhere at the Superalgos Platform Client. 
 It provides access to all modules built for the Task Server.
 */
 global.TS = {}