How mu-editor/mu-tate works
Mu-tate is an experimental Electron-based Python code editor. The documented application workflow is launching the Electron window and loading the editor interface; however, the sampled editor code only creates Ace editors and the sampled Mu module is a stub. The README also documents separate developer utilities for obtaining Ace and standalone Python runtimes. The UI markup and runtime wiring were not sampled, so relationships beyond those explicitly shown are omitted.
Main entry points: get_ace.py Ace updater · get_python.py Python updater · main.js Application window · js Ace assets
Components 13
Editor application
- Application window
mu/main.js - Editor interface
mu/index.html - Ace editor instances
mu/editor.js - Mu editor API
mu/js/mu.js
Runtime assets
- Ace assets
mu/js - Embedded Python
- Asset versions
versions.json
Asset utilities
- Ace updater
utils/get_ace.py - Python updater
utils/get_python.py
Other components
- User
- Electron runtime
- Ace release service
- Python release service
Connections 10
- User → Electron runtime: launches
README.md - Electron runtime → Application window: initializes
mu/main.js - Application window → Editor interface: loads
mu/main.js - Ace editor instances → Ace assets: uses
- Ace updater → Ace release service: fetches releases
utils/get_ace.py - Ace updater → Ace assets: installs assets
utils/get_ace.py - Ace updater → Asset versions: updates
utils/get_ace.py - Python updater → Python release service: fetches releases
utils/get_python.py - Python updater → Embedded Python: installs runtimes
utils/get_python.py - Python updater → Asset versions: updates
utils/get_python.py