@evothings_twitter, @phatpaul @faizaanshah @jaycassera_twitter : HyperReload and Evothings Studio both contains hyper code (both have folder named hyper that contains HyperReload code). Both also implemented port: 4042 even though Cloud based HyperReload scans for domain name and IP address. Evothings Studio and Evothings Viewer both connect to HyperReload cloud so in fact HyperReload acted as middle layer between the Studio and the Viewer.
If you run both HyperReload and Evothings-Studio locally on the same network then you will have port conflict problems since both of them are using port:4042. Obviously you want to start HyperReload first. You will be able to connect to it with the Viewer App by modifying the URL in the settings but Evothings-Studio wont work unless you change its own port address to something else and not 4042.
Also there are still some Ruby code around building HyperReload and some hard-coded paths and folders.
I will be doing some more exploration of them, built them in the past so it will nice to revisit those knowledge again
Evothings-Viewer ==> App.js; study it very well.
Evothings-Studio ==> Hyper/setting/setting.js; Also most the files inside the hyper/server folde e.g. file-server.js; app, uuid, monitor, etc.. are important core to understanding how inter-process communication between those there packages work and exchange data
HyperReload: ==> again see the hyper folder and look at hyper-server.js (to see how server-base(URL) App-path, IP-address, etc... are set-up). The webserver.js (mini webserver that host HyperReload). Have fun!
See Also: MoSync and Reload: this is where its all began
Ping @gokr @mikaelkindborg
Has anyone had success running evothings with a create-react-app project? I have a react project which I am building for desktop (electron), mobile (evothings / cordova), and web.
Running the project with evothings is almost completely working. The main trouble I have is that the index.html file evothings reads is not the index.html that the webpack dev-server generates. I've had some success by making these two files very similar, but some things still don't work, like the CSS generated by the styled-components library. This is broken because the CSS get's dynamically injected into the head of the index.html file.
Does anyone know how to direct evothings to read the index.html output from webpack dev-server?
1: open Virtualbox, after you start trying to build - the VM will be created and running already
2: login with user 'vagrant' password the same
3: type: vim /vagrant/result/stakcell/android/gradle/wrapper/gradle-wrapper.properties
4: edit the http address to https
I hope this will work..atleast it's a step forward in getting it to work :)