Currently, I save the contents of the editor & library for both the last English and French session, loading up the one I use based on whether world.html or monde.html is loaded. This doesn't work so well locally (using the python server) as it does when loading from the official site.
"Normal" users do not need to be able to resume their last programming session in a different language. To simplify the code, I will save the last content of the editor and library in a single place, while keeping track of the last programming language used, the last UI state used (blockly, editor, repl), and the last human language used. For now, if the last human language used is different from that which is loaded, I should log this in the javascript console. Eventually, instead of separate monde.html, world.html, world_ko.html, etc., a single html page with human language choices will be created, and the last human language recorded will determine the UI.
Currently, I save the contents of the editor & library for both the last English and French session, loading up the one I use based on whether world.html or monde.html is loaded. This doesn't work so well locally (using the python server) as it does when loading from the official site.
"Normal" users do not need to be able to resume their last programming session in a different language. To simplify the code, I will save the last content of the editor and library in a single place, while keeping track of the last programming language used, the last UI state used (blockly, editor, repl), and the last human language used. For now, if the last human language used is different from that which is loaded, I should log this in the javascript console. Eventually, instead of separate monde.html, world.html, world_ko.html, etc., a single html page with human language choices will be created, and the last human language recorded will determine the UI.