How aardio/imtip works
Project type and purpose
• This is a desktop‐assistant application (“ImTip 智能桌面助手”) written in the Aardio scripting language.
File structure
• Top level:
• main.aardio – entry point
• default.aproj – Aardio project file
• lib/ – core library modules, subdivided into:
– app/ (filterWindows, hotkey, jab wrapper for Java AccessBridge, util submodules)
– fonts (embedded font resources)
– config.aardio, style.aardio, tsfInput.aardio (input‐state tracking)
• codes/ – sample .aardio scripts (filter.aardio, hotkey.txt)
• screenshots/ – documentation images
• No separate “frontend/backend” folders; it’s a monolithic, event‐driven desktop tool.
Key insights from README
• Hooks into IME and keyboard state (tsfInput, filterWindows)
• Defines programmable hotkeys (lib/app/hotkey) that can call AI or local utilities
• Dialogs for AI chat, settings, search (dlg/*.aardio)
• Uses external Aardio extension libraries (string.words, table.coca2000, web.edgeTextToSpeech, java.accessBridge)
• Tray menu for quick toggles (lib/ui/appTrayMenu)
Core components
a. Main components:
1) Aardio Runtime (the standalone EXE engine)
2) Main Script (main.aardio + default.aproj)
3) Core Libraries (lib/*)
– Input‐State Tracker (tsfInput, filterWindows)
– Hotkey Manager (lib/app/hotkey)
– UI Modules (tray menu, colorPicker, pinyinMenu)
– Utility & Config (style, config, fonts)
4) Dialog Layer (dlg/*.aardio windows and templates)
5) Sample/Extension Scripts (codes/)
6) External Dependencies:
– OS hooks (IME, keyboard)
– Aardio extension libs (JAB, speech)
– AI/Cloud APIs (translation, dictionary, large-model chat)
7) Assets (images, screenshots, fonts)
b. Relationships & interactions:
• The Aardio Runtime launches main.aardio → loads default.aproj → initializes config → registers input‐state tracker and hotkey listeners.
• Hotkey Manager listens for defined key combos → invokes either local utilities (math, date format) or AI/Cloud API calls (via web.edgeTextToSpeech or custom HTTP calls) → opens AI Chat dialog.
• Tray Menu UI provides toggles for features (super hotkeys, IME state hints) → triggers config updates.
• Utility modules provide shared functions (clipboard, theming, JSON parsing, etc.).
c. Architectural patterns & principles:
• Modular layering: Core (input + hotkey) → UI → Dialogs → Extensions
• Event‐driven, callback‐based communication
• Plug‐in extensibility via “codes” and external Aardio libraries
• Single‐process, in‐memory modules for low latency
d. Key technologies/frameworks:
• Aardio scripting runtime & project system
• Windows IME/TSF APIs (tsfInput.aardio)
• Java Access Bridge (via lib/app/jab.aardio)
• Web/Edge TTS (web.edgeTextToSpeech)
• External AI APIs (HTTP calls, JSON)
Detailed capture of essential elements
• Don’t omit:
• The “codes” folder (extensibility demos)
• External extension libraries (JAB, TTS)
• The event bus/callback chain between input tracker → UI → dialogs
• Tray menu as an entry point for toggling features