Challenge Overview
For the Hercules client, we build a lot of web apps that run on an embedded environment. The web browser used on the embedded system is older and has compatibility issues with modern desktop browsers. This means we spend a lot of time working through compatibility issues.
In an effort to catch these issues earlier, we would like to generate a build of the embedded browser that runs on OS X (and eventually Windows and Linux). This will allow us to more easily test the web apps without having to use the embedded environment.
Code
The embedded browser can be found here for Raspberry Pi: https://github.com/Metrological/buildroot
This repo holds a set of code that can be flashed to an rPi for testing. The app we are targeting is the "qtbrowser" executable. It does appear that the code is here as well: https://github.com/Metrological/qtbrowser
Debug output / JS console
It's important that the developers be able to view the Javascript console when a page loads. This can be via the console or via a remote debugger - either is fine. The main goal is to ensure we can get the JS console output to view any errors that crop up when testing.
Build
Your deployment instructions must contain information on how to:
* Get the code
* Install the dependencies for OS X
* Build the browser app
* Run the app, ensuring the results can be displayed in a window
* Get the debug output
Markdown
The deployment guide can be provided in Markdown format. No video is required.
In an effort to catch these issues earlier, we would like to generate a build of the embedded browser that runs on OS X (and eventually Windows and Linux). This will allow us to more easily test the web apps without having to use the embedded environment.
Code
The embedded browser can be found here for Raspberry Pi: https://github.com/Metrological/buildroot
This repo holds a set of code that can be flashed to an rPi for testing. The app we are targeting is the "qtbrowser" executable. It does appear that the code is here as well: https://github.com/Metrological/qtbrowser
Debug output / JS console
It's important that the developers be able to view the Javascript console when a page loads. This can be via the console or via a remote debugger - either is fine. The main goal is to ensure we can get the JS console output to view any errors that crop up when testing.
Build
Your deployment instructions must contain information on how to:
* Get the code
* Install the dependencies for OS X
* Build the browser app
* Run the app, ensuring the results can be displayed in a window
* Get the debug output
Markdown
The deployment guide can be provided in Markdown format. No video is required.