App Mockup for a Raytracer

The task is to create a static design for a desktop app that is based on HTML/CSS/JS. The app is a simple raytracer project that will let users load scene files, change rendering parameters and view the resulting image. The user will need to be able to perform the following actions: 1. Load a new scene description file from the filesystem. 2. View and change rendering parameters. Parameters panel will be organized in sections for rendering parameters, camera parameters etc. Each section will have their own settings that can change dynamically based on drop down selection (see screenshots). The specific parameters will need to be configurable and it should be easy to edit and add new parameters. 3. Click the Start button to start the rendering. 4. Click the Stop button to stop the rendering. Start and Stop buttons must have two states: active (clickable) and disabled (not clickable) 5. When the rendering is in progress, there must be a progress bar along with a textual explanation of the current step (e.g. "Reading the scene file", "Precomputing irradiance" etc.) 6. View the image, zoom in, zoom out and pan. When hovering mouse over the image, the app must show in the status bar the current X and Y coordinates of the pixel within the image (must work correctly for zoomed images!), as well as the pixel color value (e.g. RGB 100, 200, 150) 7. Save the resulting image to a file. 8. View logs. The app is built with [login to view URL] so it is based on the Chromium engine, therefore the design is to be done in HTML/CSS/JS. The UI must behave nicely when resizing the window, and it should be possible to resize and hide the individual panes (i.e. the settings and logs). The task is not to develop the app, but to provide all front-end assets necessary to implement it. The front-end interaction (e.g. such as zooming image etc.) must be implemented. Using open source third-party libraries is allowed, but must be confirmed. You may submit multiple HTML files to show different states of the app (e.g. active/disabled buttons, with and without progress bar etc.) Provided screenshots are very rough examples of what the app might look like, but it's not required to follow them. They are just to provide visual description of the requirements above.