Starting aw-qt should open the web UI

[ErikBjare]

Obviously not if autostarted (a flag might be helpful, that's how Syncthing does it).

[johan-bjareholt]

I don't agree with this.
If it's the first time you start the program it might be nice, but otherwise I would just find it to be annoying.
The best solution would in my opinion be that when you start it for the first time, you get a pop-up with a picture of the icon in the tray and a short text like "activitywatch is now running, right click on the tray icon to see your activity and settings"

[ErikBjare]

Added startup notification in 879b790

[ErikBjare]

Reopening due to user feedback from @JohnHamiltonNZ in Twitter DM:

Depending on how easy you want to make it for less technically Savvy users you may want it to open a link in the web browser to its location when you start application. But I understand this is development version and I had no problem opening it. 😀

That startup notification I created could also be more informative, such as including where to click to open the web UI.

[ErikBjare]

I now think that when first started/clicked, it should only open the ActivityWatch web UI if it's already running (so that a user who clicks it and wonders why nothing is happening/doesn't notice the tray icon, will at least have the web UI opened for them).

This gets a tiny bit complicated by the possibility that the user could be running multiple instances of aw-qt (one for prod and one for testing), which should then open their respective web UIs (see also #79).

[Edwardsoen]

i have briefly gone through the code, i think i can give this issue a shot.

[Edwardsoen]

added small method to auto-open webui here https://github.com/Edwardsoen/aw-qt/commit/620fd8a9f3e7ba4092cd7710b37c7d1861a6a719.
for this issue #79, i dont see any way to load the port from config file without modify aw-server, and looks like we still don't have the option to store port config persistently other than changing the code in config.py ( anyway, I think for this use-case categorizing events is a better approach than having 2 prod instances? )