Challenge Overview
The client is currently implemented in Javascript, runs in a web browser, and uses http://www.pixijs.com/ for WebGL and Canvas rendering. The code can also run in a custom drawing framework called pxScene.
The code has gone through many, many iterations over a number of years and we recently brought it up to date with changes to the code structure and packaging.
This challenge will:
* Fix some bugs noted in the last challenge review and subsequent testing
* Investigate performance issues and implement profiling tools to help with future performance work
Code
Access to the code will be covered by information in the forum. Note that this challenge will cover the "develop" branch in Gitlab. Don't use "master".Bugs
These bugs must be fixed in your submission:
* https://gitlab.com/Hercules-XREReceiver/js-xre-receiver/issues/268
* https://gitlab.com/Hercules-XREReceiver/js-xre-receiver/issues/269
* https://gitlab.com/Hercules-XREReceiver/js-xre-receiver/issues/270
* https://gitlab.com/Hercules-XREReceiver/js-xre-receiver/issues/271
* https://gitlab.com/Hercules-XREReceiver/js-xre-receiver/issues/272
Latest code:
Please target commit hash 0a5309b4149e51fbc46c497d3e9323195c5a9ed8 in the "develop" branch in Git.
pxscene
Your submission must run properly both in the browser and in pxscene. You must target the latest version of pxscene. You can download the Mac app here: http://www.pxscene.org/. You can also build your own version of pxScene for Linux, but you must use a commit hash that is current when this challenge launched.
Deployment
Currently, the code is just deployed to Heroku by pushing the latest updates from Git. Heroku handles all the webpack and other packaging steps. This needs to remain in place. All configuration is done through environmental variables set on Heroku. Samples will be provided in the forum.
Reviewers should also test the Heroku deploy fully, both in the browser AND in pxscene!
Submission
Your submission must include a patch file against the Git repository and the develop branch commit hash 0a5309b4149e51fbc46c497d3e9323195c5a9ed8. Details on getting access to the Git repo can be found in the forum.
Your deployment guide must cover how to properly apply the patch.