[...] photos on the homepage do not necessarily reflect the latest development.
Solved. Sorry it took so long - have fun browsing the menus on the home page
Now the screenshots can be auto-updated every time a new build arrives.
Under the hood:
- a script that navigates the entire ML menu and saves screenshots (it runs on Jenkins,
here's a GIF)
- the following modes are simulated: photo, photo LiveView, movie
- for each top-level ML menu option: you can toggle the option (SET), navigate the submenu (Q) or do both
- nothing can be changed in submenus (yet)
- anything you have changed is discarded as soon as you go away from that menu item (to keep the number of screenshots manageable)
- extras: Canon menu, Q menus (just navigation, without changing any option)
- result: some pre-rendered screenshots (about 3000 images at the time of writing)
- some hardcoded navigation logic (that runs on the server)
- simulation state is completely given by the key sequence you see in the URL
- screenshots are served as static images
like this (will be cached by your browser)
- each screenshot has about 10K (LiveView screenshots are larger)
- URL grows with each click (but you can start over from the power button)
- front-end (interpreted by the browser)
- button overlays (the red circles) are SVG elements on top of the camera image
- works with or without JS (looks nicer with JS, e.g. flips the movie button, LED activity, nicer transitions)
- LED shows network activity (querying the next state, loading a screenshot)
- keyboard works too if JS is enabled (same buttons as in QEMU); ESC to disable keybindings, ENTER to re-enable
- browser back button works too
