activitywatch / aw-tauri Goto Github PK

We have this in aw-client for watchers: (https://github.com/ActivityWatch/aw-client/blob/master/aw_client/singleinstance.py)

Tauri has it here: https://beta.tauri.app/features/single-instance/

Needs Tauri 2.0 as @brayo-pip pointed out.

We should support non-watcher modules like aw-sync, aw-notify, etc. Naming in the code should reflect this.

Example:

-WatcherMessage
+ModuleMessage
-start/stop_watcher(s)
+start/stop_module(s)

https://beta.tauri.app/features/autostart/

Needs Tauri 2.0 (beta) as @brayo-pip pointed out.

To avoid situations like this for aw-qt, where people expect a window to open and don't notice the tray icon: https://forum.activitywatch.net/t/activity-watch-wont-launch-on-windows/1389

Possible features, in increasing order of difficulty:

• When app is started and already running, open webview.
• Add notification when ActivityWatch starts (as we used to), add setting to turn it off.
• Proper onboarding experience when app is started for the first time (or onboarding never shown), introducing ActivityWatch and the tray icon.

Options:

1. Adopt Tauri way of bundling web assets.
2. Keep using aw-server-rust bundled web assets, simply changing the starting URL and removing the placeholder app.

Not sure what the project structure would look like afterwards. Ideally, we'd have a top-level Rust project (no more src-tauri/).

Currently we use port 5666, but we use the same storage location (problematic).

We need to figure out how to deal with this, either by using a different storage location, or by using the same port and using #15 to also check that aw-qt is not running for the same port.

First listing the running/stopped or crashed modules first. Then the list of all discovered modules in path. The consistency would help users find common modules they use fast.