This is a showcase example for the "js" and "wasm" targets and also the new JavaScript API of therecipe/qt
For general information about therecipe/qt
, checkout: https://github.com/therecipe/qt
The Qt API Docs can be found here: https://doc.qt.io/qt-5/classes.html
If you have questions, join our Slack channel #qt-binding (invite yourself here)
If you are already familiar with qtdeploy and the docker deployments then just pull the "js" or "wasm" image and deploy with qtdeploy -docker build js
or "wasm" as usual.
If you are new and want to build this yourself, then just take the following steps:
-
Install Go: https://golang.org/dl/
-
Install Git: https://git-scm.com/downloads
-
Install tooling:
go get -u -v github.com/therecipe/qt/cmd/...
-
Pull the repo:
go get -d -v github.com/therecipe/widgets_playground
-
Install Docker: https://store.docker.com/search?offering=community&type=edition
-
Pull the "js" or "wasm" image:
docker pull therecipe/qt:js
or
docker pull therecipe/qt:wasm
-
Run the deployment: (replace "js" with "wasm" for an full WebAssembly build)
cd $(go env GOPATH)/src/github.com/therecipe/widgets_playground $(go env GOPATH)/bin/qtdeploy -docker build js
-
You should find the deployed application in the
deploy/js
ordeploy/wasm
subdir -
Open
deploy/{js|wasm}/index.html
with your browser
You can most of the time use qtdeploy -docker -fast build js
after you made some minor changes, heavier changes like the introduction of new Qt classes or functions, or changes inside the JavaScript files will force you to compile without the "-fast" flag once again.
It's planned to remove these limitations in the future.