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 update the existing app with a completely new UI that the client has asked us to work on, based on an existing UI they have for other products.
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/showcase-app/issues/37
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/38
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/40
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/41
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/42
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/43
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/45
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/46
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/51
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.
Make sure your submission includes:
* An updated, deployable project that includes the required changes, via a git patch
* Deployment documentation, including how to deploy to Heroku
* Validation documentation for loading the project in pxscene from Heroku
This challenge will update the existing app with a completely new UI that the client has asked us to work on, based on an existing UI they have for other products.
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/showcase-app/issues/37
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/38
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/40
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/41
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/42
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/43
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/45
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/46
* https://gitlab.com/hercules-pxscene-showcase/showcase-app/issues/51
Performance
Performance is important for this challenge. Navigation should be snappy, and pages and images should load quickly. You shouldn't change anything to hamper performance. Please note that recent changes have been made to the v1 UI in the "develop" branch. You must port those changes over to the v2 app to ensure proper performance on the set top boxes (very slow CPU and only 512MB of RAM).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
You should submit your code as a patch file against Git commit hash 7e311715240434b3c39c9865b1a5227c475e0a37 or later on the ui_v2 branch. Git details can be found in the forumMake sure your submission includes:
* An updated, deployable project that includes the required changes, via a git patch
* Deployment documentation, including how to deploy to Heroku
* Validation documentation for loading the project in pxscene from Heroku
* A video is required for this challenge.