Compiling #77
Description
Hi SkyzohKey,
Okay, I switched to my Linux Mint 18.3 (Ubuntu 16.04) system, and to this GitHub page for further comments, etc...
Why don't I see options for attaching a file or images to your GitHub for this?
-
I updated to the current versions of nodejs and npm using the PPA instructions from the link below
How To Install Node.js on Ubuntu 16.04 DigitalOcean
https://www.digitalocean.com/community/tutorials/how-to-install-node-js-on-ubuntu-16-04 -
Per your instructions of compiling from here, I cloned this to a "toxclient" folder.
ran "npm install" got these results:
`npm WARN deprecated babel-preset-es2015@6.24.1: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!
uglifyjs-webpack-plugin@0.4.6 postinstall /home/user69/toxclient/node_modules/@storybook/react/node_modules/webpack/node_modules/uglifyjs-webpack-plugin
node lib/post_install.js
uglifyjs-webpack-plugin@0.4.6 postinstall /home/user69/toxclient/node_modules/uglifyjs-webpack-plugin
node lib/post_install.js
electron@1.8.3 postinstall /home/user69/toxclient/node_modules/electron
node install.js
npm WARN eslint-config-react-app@2.1.0 requires a peer of babel-eslint@^7.2.3 but none is installed. You must install peer dependencies yourself.
npm WARN react-native@0.54.2 requires a peer of react@^16.3.0-alpha.1 but none is installed. You must install peer dependencies yourself.
npm WARN The package babel-core is included as both a dev and production dependency.
npm WARN The package babel-jest is included as both a dev and production dependency.
npm WARN The package jest is included as both a dev and production dependency.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.1.3 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: app-builder-bin-win@1.5.0 (node_modules/app-builder-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for app-builder-bin-win@1.5.0: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: app-builder-bin-mac@1.5.0 (node_modules/app-builder-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for app-builder-bin-mac@1.5.0: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-win@2.2.0 (node_modules/7zip-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-win@2.2.0: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: 7zip-bin-mac@1.0.1 (node_modules/7zip-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for 7zip-bin-mac@1.0.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
added 2263 packages in 48.262s
`
Next, I ran "npm run electron", and the application came up with the message below.
`Something is already running on port 3000. Probably:
node scripts/start.js (pid 2058)
in /home/user69/Apps-Misc/client-master
Would you like to run the app on another port instead? (Y/n)
user69@lm18 ~/toxclient $`
I can use other tox clients without port issues? Do I need to use another port, if so what port do you recommend? And the app came up without allowing me to answer "y".
The application came up with a code window on the right which I closed, asking for my username and password, but it is showing your demo(?) contact list, not my contact list. I see no way to import or use my previous tox profile? I also noticed that this created a "tox-universal-client" folder underneath my ".config" folder, is this the application configuration folder or does it also use the "tox" folder? I copied my phd21.tox profile file into this folder and made another copy of it as "tox_save.tox", but it still does not bring up my profile. I think it would be really nice if all the Tox developers used their own Tox configuration folders rather than the default Tox configuration folder to reduce possible interference when using multiple tox software clients.
It also shows "Konv", not Universal Tox Client or Tox Universal Client.
I did not see any setup or configuration options for adding contacts, audio and video, interface, profile import or export, copy ToxID, etc...
Update: I just ran this using the command "npm run web", still did not like port 3000, so I said use a different one and it chose 3001, and it brought up my default Chrome browser and a new tab without the code window, but still with the demo contact list. This was what my console terminal showed.
Starting development server ...
when I exited the application.
`Compiled successfully!
You can now view tox-universal-client in the browser.
Local: http://localhost:3001/
On Your Network: http://192.168.1.223:3001/
Note that the development build is not optimized.
To create a production build, use yarn build.
`
It looks really great. I am looking forward to trying this out...
Best regards,
Phil
phd21mint@gmail.com