Renamed ubuntu-server.js to js-executor.js

Author: vkjr

.circleci/config.yml

@@ -90,8 +90,8 @@ jobs:
         background: true
 
       - type: shell
-        name: Start react-native-desktop's ubuntu-server.js
-        command: node ./ubuntu-server.js
+        name: Start react-native-desktop's js-executor.js
+        command: node ./js-executor.js
         background: true
 
       - run:

Examples/2048/qml/run-example.sh.in

@@ -1,5 +1,5 @@
 #!/bin/bash
 
-(node ${CMAKE_SOURCE_DIR}/ubuntu-server.js 2>&1 > /dev/null) &
+(node ${CMAKE_SOURCE_DIR}/js-executor.js 2>&1 > /dev/null) &
 qmlscene -I ${CMAKE_BINARY_DIR}/ReactQt/runtime/src/ ${CMAKE_CURRENT_BINARY_DIR}/${EXAMPLE_NAME}.qml
 

Examples/ActivityIndicator/qml/run-example.sh.in

@@ -1,5 +1,5 @@
 #!/bin/bash
 
-(node ${CMAKE_SOURCE_DIR}/ubuntu-server.js) &
+(node ${CMAKE_SOURCE_DIR}/js-executor.js) &
 qmlscene -I ${CMAKE_BINARY_DIR}/ReactQt/runtime/src/ ${CMAKE_CURRENT_BINARY_DIR}/${EXAMPLE_NAME}.qml
 

Examples/Movies/qml/run-example.sh.in

@@ -1,5 +1,5 @@
 #!/bin/bash
 
-(node ${CMAKE_SOURCE_DIR}/ubuntu-server.js 2>&1 > /dev/null) &
+(node ${CMAKE_SOURCE_DIR}/js-executor.js 2>&1 > /dev/null) &
 qmlscene -I ${CMAKE_BINARY_DIR}/ReactQt/runtime/src/ ${CMAKE_CURRENT_BINARY_DIR}/${EXAMPLE_NAME}.qml
 

Examples/UIExplorer/qml/run-example.sh.in

@@ -1,5 +1,5 @@
 #!/bin/bash
 
-(node ${CMAKE_SOURCE_DIR}/ubuntu-server.js 2>&1 > /dev/null) &
+(node ${CMAKE_SOURCE_DIR}/js-executor.js 2>&1 > /dev/null) &
 qmlscene -I ${CMAKE_BINARY_DIR}/ReactQt/runtime/src/ ${CMAKE_CURRENT_BINARY_DIR}/${EXAMPLE_NAME}.qml
 

Examples/run-example.sh.in

@@ -1,5 +1,5 @@
 #!/bin/bash
 
-(node ${CMAKE_SOURCE_DIR}/ubuntu-server.js) &
+(node ${CMAKE_SOURCE_DIR}/js-executor.js) &
 qmlscene -I ${CMAKE_BINARY_DIR}/ReactQt/runtime/src/ ${CMAKE_CURRENT_BINARY_DIR}/${EXAMPLE_NAME}.qml
 

RNTester/qml/run-example.sh.in

@@ -1,5 +1,5 @@
 #!/bin/bash
 
-(node ${CMAKE_SOURCE_DIR}/ubuntu-server.js) &
+(node ${CMAKE_SOURCE_DIR}/js-executor.js) &
 qmlscene -I ${CMAKE_BINARY_DIR}/ReactQt/runtime/src/ ${CMAKE_CURRENT_BINARY_DIR}/${EXAMPLE_NAME}.qml
 

ReactQt/runtime/src/communication/serverconnection.cpp

@@ -16,7 +16,7 @@
 
 namespace {
 QString default_executable{"node"};
-QString default_script{"ubuntu-server.js"};
+QString default_script{"js-executor.js"};
 QStringList default_arguments{"--pipe"};
 
 QString itemWithPath(const QString& item, const QStringList& searchPaths) {

docs/ContributorEnvSetup.md

@@ -66,7 +66,7 @@ To do this execute following commands in different terminals:
 npm start #starts bundler
 ```
 ```sh
-node ubuntu-server.js #starts js server
+node js-executor.js #starts js server
 ```
 
 Like you do when [run your new app](CreateNewApp.md#run-the-project)

docs/CreateNewApp.md

@@ -37,7 +37,7 @@ If you're using macOS, run these commands in 2 different shells (from `DesktopSa
 npm start #starts bundler
 ```
 ```sh
-node node_modules/react-native/ubuntu-server.js #starts js server
+node node_modules/react-native/js-executor.js #starts js server
 ```
 
 Afterwards, in a 3rd shell execute:
@@ -48,7 +48,7 @@ Compilation of desktop project will start. When it finished and app run you can
 
 ![](./media/react-native-desktop-new-app.png)
 
-**Note:** On non-macOS systems, `npm start` and `node ubuntu-server.js` will be executed automatically by the above command(`react-native run-desktop`)
+**Note:** On non-macOS systems, `npm start` and `node js-executor.js` will be executed automatically by the above command(`react-native run-desktop`)
 
 
 **If you want to know why you had to start bundler and js server** - check the doc on [how react-native-desktop works internally](./HowRNDesktopAppWorks.md)

docs/FAQ.md

@@ -25,15 +25,15 @@ It was forked from Canonical/react-native-linux. Canonical in its turn forked fa
 
 ### Does the bundler step in the diagram only happen once at app startup or is all of the JS code appended to a single file on every reload?
 
-On every reload Qt app requests single js files and sends it to execution in ubuntu-server. It is like restart, but quicker. Bundler caches that js file, so collecting it together doesn’t take much time.
+On every reload Qt app requests single js files and sends it to execution in js-executor. It is like restart, but quicker. Bundler caches that js file, so collecting it together doesn’t take much time.
 
 ### Is there a dedicated node mule within react-native for communicating with qt at the javascript code level or does that happen elsewhere, say, in the build pipeline?
 
 No. React-native is designed to have own js part and communication with native part.
 Qt code in react-native-desktop contains a bunch of modules that implement controls and API’s natively.
 When Qt Application starts it sends `config` - information about what modules it implements on native side - their names, ids, lists of functions, constants, etc. From this moment react-native part of js code can “invoke” that native methods just by mentioning them in JSON results.
 
-Here is an example communication between Qt app and ubuntu-server. In the app there is a button that changes color when pressed.
+Here is an example communication between Qt app and js-executor. In the app there is a button that changes color when pressed.
 
 When user clicks button, we send following code line for execution in Js:
 `__fbBatchedBridge.callFunctionReturnFlushedQueue(\"RCTEventEmitter\",\"receiveEvent\",[2,\"topPress\",{}]);`

docs/HowRNDesktopAppWorks.md

@@ -13,7 +13,7 @@ When you create a project with `react-native init SomeProject`, you have ios and
 There are 3 participants in react-native-desktop application:
 - Qt application
 - Bundler
-- JS server (right now called ubuntu-server, but this is subject to change)
+- JS server (right now called js-executor, but this is subject to change)
 
 `Qt application` - built from a project in `desktop` folder. When runs it establishes communication with JS server and shows appropriate UI.
 

docs/InspectJs.md

@@ -8,15 +8,15 @@
 
 1) Run js server with `--inspect` switch:
 ```sh
-node --inspect ubuntu-server.js
+node --inspect js-executor.js
 ```
 
 2) Run your `react-native-desktop` application
 
 3) Open `chrome://inspect` page in a Chrome browser
 ![](media/devtools-inspect-target.png)
 
-4) Click on `inspect` link near `ubuntu-server.js` Target
+4) Click on `inspect` link near `js-executor.js` Target
 
 5) Chrome devtools will open where you can see console output of your application and debug it.
 

ubuntu-server.js renamed to js-executor.js

@@ -52,7 +52,7 @@ fi
 # For net case, try and run executor; it is probably OK if this fails - it's
 # just running elsewhere
 if [[ "$executor" == "ReactNetExecutor" ]]; then
-  (node @CMAKE_BINARY_DIR@/bin/ubuntu-server.js 2>&1 > /dev/null) &
+  (node @CMAKE_BINARY_DIR@/bin/js-executor.js 2>&1 > /dev/null) &
 fi
 
 # if [[ $on_device == 1 ]]; then

local-cli/generator-desktop/templates/run-app.sh.in

@@ -110,7 +110,7 @@ function _copyBinaries(args, packagePath, resolve, reject) {
   console.log(chalk.bold('Copying app binaries...'));
   const binDestPath = path.join(packagePath, 'bin');
   mkdirp.sync(binDestPath);
-  child_process.exec('cp -uR ' + path.join(args.root, 'desktop/bin/ubuntu-server.js ') + binDestPath + ' || true',
+  child_process.exec('cp -uR ' + path.join(args.root, 'desktop/bin/js-executor.js ') + binDestPath + ' || true',
                       {}, (error, stdout, stderr) => {
                         if (error)
                           reject(error);

local-cli/runDesktop/packageDesktop.js

@@ -99,9 +99,9 @@ function startPackagerInNewWindow() {
 
 function startUbuntuServerInNewWindow() {
   if (process.platform === "win32") {
-    child_process.spawn('cmd', ['/c', 'node ./desktop/bin/ubuntu-server.js'],{detached: true});
+    child_process.spawn('cmd', ['/c', 'node ./desktop/bin/js-executor.js'],{detached: true});
   } else {
-    child_process.spawn('gnome-terminal', ['-e', 'node ./desktop/bin/ubuntu-server.js'],{detached: true});
+    child_process.spawn('gnome-terminal', ['-e', 'node ./desktop/bin/js-executor.js'],{detached: true});
   }
 }