How matteo-peronnet/plancktimetracker works
Main Application Architecture
a) Electron Components:
• Main Window (mainWindow.js)
• System Tray (planckTray.js)
• Auto Updater (updater.js)
b) Frontend Application:
• Components Layer
• Views/Layouts Layer
• Store (Redux) Layer
• Services Layer
c) External Services:
• Connections to any backend services the app communicates with
Detailed Component Breakdown
Frontend Architecture (React):
a) Views Layer:
• Home
• Login
• Project
• Task
• Timer (with sub-components for Steps)
b) State Management:
• Ducks (Redux modules):
• app
• intl
• planck
• timer
• user
• Middleware
• Services:
• authentication
• customer
• task
• timeSpent
• timeSpentType
c) Supporting Systems:
• i18n (Internationalization)
• Routes
• Components
Data Flow
• IPC (Inter-Process Communication) between Electron and React
• Redux action/state flow
• Service API calls
• Event handling paths
Specific Elements
• System tray integration
• Time tracking core functionality
• Authentication flow
• Internationalization system
• Route protection (isPrivate.js)
• User session handling
Technical Details to Note
Annotations for:
• Webpack configuration
• Build process
• Update mechanism
• Environment configurations
[Electron Shell]
• [Main Process]
• Main Window
• System Tray
• Auto Updater
• [Renderer Process]
• [React Application]
• Components
• Views/Layouts
• Providers
• [Redux Store]
• Ducks
• Middleware
• Services
• [Supporting Systems]
• i18n
• Routes
• Utils
Important Considerations:
Update mechanism flow
Remember to indicate the build and deployment pipeline, as the presence of webpack configs and CI/CD files suggests this is an important aspect of the system.