How stratopedia/ai-translation-engine works
This desktop code editor lets a user write code in a language tab, translate it into the other supported languages with Gemini, or run the active tab in a temporary workspace. The GUI coordinates translation and execution on background threads and displays logs in its console. The graph separates the UI, translation service, and execution sandbox; compiler/runtime tools and Gemini are external dependencies. Relationships reflect the sampled source and README; no additional internal stages are inferred.
Main entry points: gui.py Language workspaces · runner.py Sandbox runner · ai_engine.py AI translation engine · main.py App launcher
Components 12
Desktop interface
- App launcher
main.py - Language workspaces
gui.py - Translation workflow
gui.py - Execution workflow
gui.py - Live output console
gui.py
AI translation
- AI translation engine
ai_engine.py - Code fence cleanup
ai_engine.py
Code execution
- Sandbox runner
runner.py - Temporary workspace
runner.py
External services
- Gemini API
- Language toolchains
Other components
- Engineer
Connections 14
- Engineer → App launcher: launches
readme.md - App launcher → Language workspaces: creates
main.py - Engineer → Language workspaces: edits code
readme.md - Language workspaces → Translation workflow: starts translation
gui.py - Translation workflow → AI translation engine: requests translations
gui.py - AI translation engine → Gemini API: requests code
ai_engine.py - AI translation engine → Code fence cleanup: cleans response
ai_engine.py - Translation workflow → Language workspaces: updates tabs
gui.py - Translation workflow → Live output console: reports status
gui.py - Language workspaces → Execution workflow: selects active code
gui.py - Execution workflow → Sandbox runner: executes code
gui.py - Sandbox runner → Temporary workspace: writes code
runner.py - Sandbox runner → Language toolchains: compiles and runs
runner.py - Sandbox runner → Live output console: sends logs
gui.py