There are two parts to this: a) How to user graphical constructions (we call them parts) outside of the main framework? We currently work on ways to "snapshot

There are two parts to this: a) How to user graphical constructions (we call them parts) outside of the main framework? We currently work on ways to "snapshot" them in a way that they include all their dependencies. So not just the object (graph) state but really all code dependencies. es6 modules are a big help here since they allow to trace dependencies statically. This is work in progress and we will post updates about this. The state right now is that you can the HTML view of morphs into web pages, e.g. see [2] b) Several parts of the system can be used standalone, e.g. you can enable support for Lively tooling in node.js processes or arbitrary webpages. See https://lively-next.org/worlds/lively-2-webpage https://lively-next.org/worlds/lively-2-webpage for a bookmarklet that loads the lively.vm [1] and lively-system-interface on a arbitrary web page: https://imgur.com/a/2foGR https://imgur.com/a/2foGR. This allows you to then use the workspaces, system browser, inspectors, etc. on remote targets. [1] https://livelykernel.github.io/lively.vm/ https://livelykernel.github.io/lively.vm/ [2] https://lively-next.org/worlds/lively.next%20website https://lively-next.org/worlds/lively.next%20website