How torhal/frenemy works
Main Components
A. Core Module Layer:
• Main "Frenemy.lua" as the core controller
• "DataObject.lua" as it appears to be a crucial data management component
• "_Main.lua" files as entry points for each major module
B. Feature Modules:
1. TooltipHandler Module:
• Specialized handling for Battle.net, Guild, and WoW Friends
• SpecializedCells submodule
• To the Render.lua component
2. Common Module:
• MapHandler for zone management
• Sorting component for list management
• Debugger for development support
3. Preferences Module:
• DataObject and Tooltip components
• Configuration management flow
C. Localization Layer:
• Supported languages
• Connection to other modules
[Core Layer]
• ↓
[Feature Modules] ← → [Localization Layer]
• ↓
[WoW API Integration]
Specific Design Elements
• Use rectangles for main modules
• Use rounded rectangles for submodules
• Use diamonds for data objects
• Blue: Core components
• Green: Feature modules
• Yellow: Data management
• Purple: UI components
• Gray: External interfaces (WoW API)
Data Flow Representation
Following key interactions:
• Data flow from WoW API to the core module
• Information processing through the TooltipHandler
• User preference management flow
• Localization integration points
Important Architectural Patterns to Highlight
• Module Pattern: Show how each major component is self-contained
• Observer Pattern: For tooltip and UI updates
• Command Pattern: For handling user interactions
• Facade Pattern: For WoW API interactions
Technical Details
• XML embedding system (reference embeds.xml)
• Manifest files relationships
• Type definitions from @types directory
• Configuration management through .pkgmeta
• Line styles
• Abbreviations used
• Module relationships
This will create a comprehensive visualization of how Frenemy works as a WoW addon while maintaining clarity about its architecture and component interactions.