@see how Manta does it.

Also setup a crowdin org for the translations.

From the repository description:

The Universal Tox client. Platform-agnostic Tox client with user-friendlyness in mind! http://beta.tox.chat

From README.md:

You can live preview most of the components on The Storybook!

This needs to be implemented if we want to make some releases c:
https://electron.build

Currently yarn build is broken on master (https://travis-ci.org/TheToxProject/client/builds/355266086).

(If the fix is not trivial and takes some time, I think the commits that broke master should be reverted.)

https://github.com/Tox-Client/client/blob/83468d7c6fe6122580c6ab2cd05adfcb9b658777/package.json#L21

Please provide the AppImage for download on https://github.com/Tox-Client/client/releases.

This PR, when merged, will compile this application on Travis CI upon each git push, and upload an AppImage to your GitHub Releases page.

Providing an AppImage would have, among others, these advantages:

• Applications packaged as an AppImage can run on many distributions (including Ubuntu, Fedora, openSUSE, CentOS, elementaryOS, Linux Mint, and others)
• One app = one file = super simple for users: just download one AppImage file, make it executable, and run
• No unpacking or installation necessary
• No root needed
• No system libraries changed
• Works out of the box, no installation of runtimes needed
• Optional desktop integration with appimaged
• Optional binary delta updates, e.g., for continuous builds (only download the binary diff) using AppImageUpdate
• Can optionally GPG2-sign your AppImages (inside the file)
• Works on Live ISOs
• Can use the same AppImages when dual-booting multiple distributions
• Can be listed in the AppImageHub central directory of available AppImages
• Can double as a self-extracting compressed archive with the --appimage-extract parameter

Here is an overview of projects that are already distributing upstream-provided, official AppImages.

If you have questions, AppImage developers are on #AppImage on irc.freenode.net.

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 [email protected]: 🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read babeljs.io/env to update!

[email protected] postinstall /home/user69/toxclient/node_modules/@storybook/react/node_modules/webpack/node_modules/uglifyjs-webpack-plugin
node lib/post_install.js

[email protected] postinstall /home/user69/toxclient/node_modules/uglifyjs-webpack-plugin
node lib/post_install.js

[email protected] postinstall /home/user69/toxclient/node_modules/electron
node install.js

npm WARN [email protected] requires a peer of babel-eslint@^7.2.3 but none is installed. You must install peer dependencies yourself.
npm WARN [email protected] 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: [email protected] (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/app-builder-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/app-builder-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/7zip-bin-win):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: wanted {"os":"win32","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: [email protected] (node_modules/7zip-bin-mac):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for [email protected]: 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
[email protected]

Roadmap

I've finally decided to make a roadmap for this project because this is a project I really believes into. Ricin & Konv has conviced me that a better IM/Tox client is possible and this project is my attempt to makes my dreams comes true! :)

Milestone 1 (v0.1.0-alpha)

Create a library (and publish it on NPM) containing the UI elements that will be used in the client. That means a LOT of small and bigger components that needs to be reusable and that MUST performs/looks the same not depending if that's run on the browser, the desktop client, or the mobile one.

Milestone 2 (v0.2.0-alpha to v0.5.0-alpha)

Create a library (and publish it on NPM) that allows to use c-toxcore on mobile devices. I will need to create a wrapper for Android in Java (I mostly know that language, so shouldn't be too hard) and one for iOS in Obj-C/Swift, which are languages I have never tried nor used, and that I'll have to learn to get this milestone right.

Milestone 3 (v0.6.0-alpha to v0.8.0-alpha)

Wire's all the components to redux and map redux actions creators to the react-toxcore library done in the previous milestone. Have everything properly working on every platform, whether it's in the browser, iOS, Android, Linux, Windows or OSX. Everything has to look exactly the same, and works the same, and even have the same bugs!

Milestone 4 (no release)

Take a break with the client development and create a small promotional website, with a blog and stuffs to aid in getting the app in user's hands. This website will need to be clear, simple and attractive. The blog will serves as a distribution channel, and thus needs to be polished and localized.

Milestone 5 (v0.9.0-beta)

Publish the app on respective App Stores (App Store, Play Store, Windows Store, and get it in AUR + Fedora + Ubuntu + Solus repos) in beta test mode, spread the word and collect users feedbacks.

Milestone 6 (v1.0.0-rc1)

Fix all the issues reported during the beta-test period and update the branding a little bit to gives beta-tester new "features", giving them more enjoyment ! Release a pre-release for 2 weeks extra bugs reports.

Milestone 7 (v1.0.0-rc2)

Finally fixes all the issues from last pre-release 2 weeks time (as they appears) and do release a 1st stable version to peoples.

Milestone 8 (v1.0.0-rc3)

Take some time to build a list of all the app's strings, prepare them for localization (ICU format), setup tooling to enable people to translate in their languages. Wait 2 weeks for translations to be done, then release.

I guess this is a pretty nice roadmap for this project and I'm willing to achieve every stuff pointed out in it to get that project in the right way. :)

Hi SkyzohKey,

Is there a working version of this available yet for Ubuntu 16.04 & Linux Mint 18.x?

Best regards,

Phil

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

• Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

Your Greenkeeper Bot 🌴

Hi SkyzohKey,

nice site, but not complete yet. Web-App, Downloads, About, Blog are empty pages.
Please set up an web version of your TOX client.

Did the project will be continued?
If it stucks in money. please contact me ;)

BR

Example for Windows 64 bits: https://downloads.tox.chat/windows/x64

Does not work for me, website inaccessible.

Is this project not maintained anymore?