Challenge Overview
The PxScene Showcase app will be an app that runs in pxscene (pxscene.org) that displays a functioning UI for browsing videos. It will be used by the client to show off the capabilities of pxscene on embedded devices.
This challenge will integrate the converted prototype with the backend REST services.
Target environment
We are targeting pxscene for this challenge. Note that pxscene applications are implemented in Javascript but use custom APIs for drawing and animations. You are expected to investigate the documentation for pxscene and implement things according to pxscene best-practices.
http://www.pxscene.org/docs/apis/index.html
https://github.com/pxscene/pxscene
Further examples can be found here:
https://github.com/pxscene/pxscene/tree/gh-pages/examples/px-reference
* https://gitlab.com/hercules-pxscene-showcase/prototype-conversion/issues/1
* https://gitlab.com/hercules-pxscene-showcase/prototype-conversion/issues/2
���* https://gitlab.com/hercules-pxscene-showcase/prototype-conversion/issues/3
���
Performance is important for this challenge. Navigation should be snappy, and pages and images should load quickly. You should implement asynchronous loading of images and data from the REST services.
Styling and general Javascript should be as clean as possible, with little to no redundancy (DRY). For instance, if each screen is a different JS file, don't copy / paste style details or redundant methods to each file.
The code should be well encapsulated, documented, and designed. This will be a reference application, so no hacks or bad code will be acceptable.
Make sure your submission includes:
* An updated, deployable project that includes the front end and backend projects in one codebase
* Deployment documentation, including how to deploy to Heroku
* A video showing a walkthrough of the updated project in pxscene
* Validation documentation for loading the project in pxscene from Heroku
This challenge will integrate the converted prototype with the backend REST services.
Target environment
We are targeting pxscene for this challenge. Note that pxscene applications are implemented in Javascript but use custom APIs for drawing and animations. You are expected to investigate the documentation for pxscene and implement things according to pxscene best-practices.
http://www.pxscene.org/docs/apis/index.html
https://github.com/pxscene/pxscene
Further examples can be found here:
https://github.com/pxscene/pxscene/tree/gh-pages/examples/px-reference
Requirements
These tickets comprise the requirements for this challenge:* https://gitlab.com/hercules-pxscene-showcase/prototype-conversion/issues/1
* https://gitlab.com/hercules-pxscene-showcase/prototype-conversion/issues/2
���* https://gitlab.com/hercules-pxscene-showcase/prototype-conversion/issues/3
���
Performance
Performance is important for this challenge. Navigation should be snappy, and pages and images should load quickly. You should implement asynchronous loading of images and data from the REST services.
Styling and redundancy
Styling and general Javascript should be as clean as possible, with little to no redundancy (DRY). For instance, if each screen is a different JS file, don't copy / paste style details or redundant methods to each file.
Code layout
The code should be well encapsulated, documented, and designed. This will be a reference application, so no hacks or bad code will be acceptable.
Submission
Make sure your submission includes:
* An updated, deployable project that includes the front end and backend projects in one codebase
* Deployment documentation, including how to deploy to Heroku
* A video showing a walkthrough of the updated project in pxscene
* Validation documentation for loading the project in pxscene from Heroku