How binary-ho/quick-memo works
Main Components
A. User Interface Layer:
• MemoToolWindow (main container)
• Components:
• MemoList
• MemoEditor
• MemoToolbar
• ToastPopup (for notifications)
B. Action Layer:
• OpenMemoAction (handles keyboard shortcuts)
• MemoActionManager (manages memo-related actions)
C. Application Layer:
• MemoService (business logic)
• MemoRepository (data access interface)
D. Infrastructure Layer:
• MemoState (persistence state)
• MemoStateRepository (state management)
• MemoMapper (data transformation)
• SavedMemos (storage implementation)
• UI Layer (Top)
• ↓
• Action Layer
• ↓
• Application Layer
• ↓
• Infrastructure Layer (Bottom)
Key Elements to Highlight
a) Plugin Integration:
• Integration point with IDE (plugin.xml configuration)
• OpenMemoAction as the main entry point
b) Data Flow:
• Memo creation/update/delete operations
• State persistence flow
• UI update mechanisms
c) Important Constraints:
• 20 memos limit
• 64KB per memo limit
Specific Implementation Details
[MemoToolWindowFactory] → [MemoToolWindow]
• ↓
[MemoList] ← [MemoEditor] ← [MemoToolbar]
• ↓
[MemoService] → [MemoRepository]
• ↓
[MemoStateRepository] → [MemoState]
Technical Stack Indicators
• JetBrains Platform SDK integration
• Kotlin build system (Gradle)
• Persistence mechanisms (IDE's built-in state management)
Remember to include annotations for:
• Entry points (keyboard shortcuts)
• User interaction flows
• Data persistence paths
• Error handling paths (e.g., MemoLimitExceededException)
This will provide a comprehensive view of how the plugin integrates with the IDE and manages its internal operations.