MX Multiverse

This will be a page for developing and testing support for multiple matrixes--simply models without parents--co-existing on a single page, along with vanilla DOM not managed by MX code.

Interesting issues:

• extending fget to work across MXes;
• reactivity across MXes;
• all the above with MX populations changing; and
• dynamic injection/removal from vanilla DOM.

results

Well this turned out interestingly. We added a "Debug" button to the trainer toolbar. Click it and it adds/removes a second mxWeb matrix whose DOM gets added/removed from a static HTML DIV.

The so-called "Debugger" simply displays a hierarchy of DIVs mirroring the structure of the current mission. Baby steps.

details

• fget is unchanged for now. Matrices can be registered in a dictionary, then retrieved explicitly and searched with fget;
• the debigger matrix follows the app matrix. A click handler in the former mutates the style of a DIV in the second;
• The debugger display shows the app structure dynamically; and
• the debugger matrix can be cleared and reinstated at will.

Code is in mxweb-trainer.mission-control.