Remaining tasks after categorization PR

[ErikBjare]

These were the leftover tasks from #145

• Merge web watcher events into window events in the query? (to allow for classifying by url/domain)
• Category Tree: If a category has children, but also activity attributed directly to the parent that does not belong to a child, then create a "Other" child containing the activity.
• Should we have a way to filter on a specific event key? Right now the regexes are applied on every (string) data value. (feat: more categorization and support for select_keys #286)
• Add a way to show how/which events are (un)categorized
• Fix summary view to also use Vuex and all the new goodies
• Improve default categories (Improving the default categories #174)
• Link to docs and/or regex101, explaining how regular expressions work and how to write good categorization rules.

[johan-bjareholt]

Merge web watcher events into window events in the query? (to allow for classifying by url/domain)

I was trying to prototype this but realized that we need a new transform to accomplish this if we want the durations to be correct. I would propose something like "union_events_split".

The reason why a new transform is needed is because we have to intersect the browser events with the window and afk events to make active time correct, but then we need to merge them back into the window event data. For this to be correct we need to union the event data where they intersect and if they don't perfectly align we need so split the events.

An example which should explain it better:

 * |---------|----------------|
 * | events1 |[a     ][b     ]|
 * | events2 |    [c     ]    |
 * | result  |[a ][ac][bc][b ]|
 * |---------|----------------|

There is the union function in aw-server-python but from the documentation I don't fully understand what it does, it seems similar but slightly different.

[pierre-lehnen-rc]

Are there still plans to implement the web/window merge?