@
mimi3
So, moOde generates and serves HTML pages full of CSS and Javascript code with just a touch of raw HTML.
The local-display function is implemented via Chrome running over X11 and rendering the same HTML pages which are served to full browsers on remote devices. (This clever scheme was birthed by a user many releases ago, back in the days when all we had for communication was a single thread on the diyAudio forum.)
The obvious approach to getting what you want is to modify each generated HTML page so that it will render differently on a local (e.g., limited) and a remote (e.g., full) display.
There's no published moOde technical guide for this.
At a minimum, you need to know CSS and Javascript to understand how the existing HTML pages are rendered in the browser.
Then, to modify the way the pages are rendered locally vs remotely, you'll need to trace back from the page contents to the constituent .js and .css files in moOde's codebase and make your changes in them (with luck, maybe just one or so .css files). Detecting whether the display is local vs remote will be a fun little sidebar exercise.
An alternative approach which springs to mind is to generate dual versions of each page, one for local (limited) and one for remote (full) displays, serve them via different IP ports, and modify the local-display configuration to read the limited version instead of the original. Now you need to know PHP too.
My personal calculation was that I couldn't do either in a finite amount of time because I'm barely literate in PHP and JS/CSS. That's why I chose a third possibility: use the information in the currentsong.txt file to populate my own display, rendering not via HTML but directly into the Linux framebuffer, using Python, a language in which I'm acceptably proficient.
YMMV
Regards,
Kent