Skip to content

Performance Optimization and Activity History Feature#16

Open
mx57 wants to merge 1 commit into
feat/desktop-pet-cat-implementation-13128440384193574434from
perf-and-history-tab-2718385397371333976
Open

Performance Optimization and Activity History Feature#16
mx57 wants to merge 1 commit into
feat/desktop-pet-cat-implementation-13128440384193574434from
perf-and-history-tab-2718385397371333976

Conversation

@mx57

@mx57 mx57 commented Jul 8, 2026

Copy link
Copy Markdown
Owner

This update focuses on both performance optimization and feature completeness.

  1. Performance (Data Layer): Introduced update_stats_batch in DataStore to perform all statistics updates (bonding points, KPS, clicks, etc.) in a single SQLite transaction. This significantly reduces I/O overhead during the flush_all process in InputManager.

  2. Feature (Activity History): Upgraded the StatsDialog to a tabbed interface.

    • Tab 1 (Progress): Displays current stats, level progress, and achievements.
    • Tab 2 (History): Shows a chronological list of recent activities (app starts, feedings, level ups, achievements, and Pomodoro sessions) fetched from the activity_log table.
  3. Logging: Added descriptive log_event calls in InputManager and TrayMenu to populate the activity history with meaningful data.

Tested with unittest and verified visually via offscreen rendering screenshots for both "Progress" and "History" tabs.


PR created automatically by Jules for task 2718385397371333976 started by @mx57

- Added `update_stats_batch` to `DataStore` for atomic SQLite updates.
- Refactored `StatsDialog` with `QTabWidget` and added "History" tab.
- Implemented `log_event` calls across the app for key interactions.
- Optimized `InputManager.flush_all` to use the new batch method.
- Verified changes with automated tests and UI screenshots.
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant