How aisingapore/tagui works
Main Components
a. Core Engine Layer:
• TagUI Core Engine (src/tagui)
• Language Processing Components (src/tagui_parse.php)
• Execution Components (src/tagui_header.js, src/tagui_footer.js)
b. Integration Layer:
• Browser Automation (Chrome/Edge support)
• Desktop Automation (via SikuliX)
• Command Line Interface
• Visual Automation & OCR
c. Extension Layer:
• MS Office Integration (Word/Excel Add-ins)
• Programming Language Bindings (Python/R/C#)
• Telegram Integration
• Node-RED Integration
d. Development Tools:
• Chrome Extension (src/chrome)
• Language Support (src/languages)
• IDE Plugins (VS Code, Notepad++)
Relationship Flows
• User Input → Language Parser → Execution Engine
• Execution Engine ↔ Browser/Desktop/CLI Interfaces
• Core Engine ↔ Integration Services
• -ins/Extensions ↔ Core Engine
Architecture Patterns
Key architectural aspects:
• Modular Design (separate components for different functionalities)
• Plugin Architecture (support for multiple languages and integrations)
• Event-Driven Architecture (for automation workflow)
• Multi-platform Support (Windows, macOS, Linux)
Key Technical Details
• File Processing Flow:
• User Script → Language Parser → JavaScript Translation → Execution Engine
• Security Layer:
• On-premise execution
• Local storage
• OS-level security
Component Grouping
Related components:
Core System:
• TagUI Engine
• Parser
• Execution Runtime
Automation Interfaces:
• Web Automation
• Desktop Automation
• Visual Automation
Extensions:
• Office Integration
• Language Bindings
• External Services