How jenova-framework/jenova-runtime works
Main Components
a) Core Components:
• Scripting System
• Script Compiler
• Script Interpreter
• Script Manager
• Script Instance Handler
• Script Templates
• Asset Management System
• Asset Monitor
• Package Manager
• Task System
• Profiler System
• GDExtension Integration Layer
b) Dependencies Layer:
• Code Generation (AsmJIT)
• Compression (LibFastZLib)
• Archive Handling (LibArchive)
• Network Operations (LibCurl)
• Compilation Backend (LibTinyCC)
• Threading (LibPThread)
• Memory Management (MemoryModule++)
• Hook System (MinHook)
• Development Tools Integration (LibVSWhere)
┌─────────────────────────────────────────────┐
• Godot Engine Layer │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• GDExtension Integration Layer │
• ┘
• ↕
┌─────────────────────────────────────────────┐
• Jenova Runtime Core │
• ┬─────────────┬────────────────┤
• Scripting │ Asset │ Task System │
• System │ Management │ & Profiler │
• ┴─────────────┴────────────────┘
• ↕
┌─────────────────────────────────────────────┐
• Dependencies & Libraries │
• ┘
Detailed Component Relationships
The Script System should be shown with internal connections:
Script Manager ─→ Script Compiler
• ↓
Script Interpreter ←→ Script Instance
• ↓
Script Templates ─→ Script Resource
Implementation Details
Use standardized UML notation where appropriate:
• Components as rectangles
• Interfaces as lollipops
• Subsystems as nested rectangles
Additional Elements
• Component types
• Connection types
• Build target specifications
• Optional/Proprietary features
• Integration points
This architecture should clearly show how Jenova Runtime serves as a bridge between C++ code and the Godot engine while highlighting its extensive feature set and modularity.