Web demo crashes upon selecting "Custom HTML" interface

[davidefiocco]

Steps to reproduce:

• Visit https://prodi.gy/demo
• In the INTERFACE drop down, select "Custom HTML"

I'm not sure what the expected behavior of this is, but the demo currently crashes and will not recover upon selecting a different INTERFACE from the drop down:

The demo is currently at version 1.9.0 at the time of writing.
However, it suffices to reload the page to restore normal behavior.

[ines (Ines Montani)]

Thanks, looks like this was a problem with the new site setup / demo server! Fixed it and the HTML example should now work as expected again

[DROMZEE]

This demo is very interesting

Is the code (js, html, recipe.py) published?

I want to change it to add a user interface language selection

[ines (Ines Montani)]

Glad you like the demo

@DROMZEE

I want to change it to add a user interface language selection

The live demo is just a demo and it doesn't actually run a recipe – it just serves static content from custom, pre-defined API endpoints. It also adds the dropdowns that just discard everything and reload the app, which is nice for a demo, but doesn't really make much sense in a "real world" application. I'm explaining a bit more about this here:

live demo like user interface

Hi! Here are two threads where I explain a few more details on why Prodigy is designed to use separate processes for different tasks and why switching between different streams and interfaces in the browser like that only really works for a demo: https://support.prodi.gy/t/multiple-recipes-same-port/933/2 That said, if you're mostly interested in having a quick way to start a different task from the browser without having to go back to the command line, you could write a mini app that lets t…

The UI language is typically set in the config on startup so there's not really a built-in way to change it at runtime, although it could be possible. (I haven't tried this yet, but one option would be to update the config of the current annotation task to overwrite it on a per-task basis – like: window.prodigy.update({ config: { ui_lang: 'fr' }}). But now sure how that behaves, it might switch back when the next task is loaded.)