3 ms·
I imagine that your event feed is going to get pretty unwieldy if you have a thousand events named like the following: div.star.empty button.btn.btn-primar
by physcab 14y ago
I imagine that your event feed is going to get pretty unwieldy if you have a thousand events named like the following:
div.star.empty
button.btn.btn-primary
button#nodisturb.muted
a.bold-text.text
Do you have any ideas how you are going to overcome this? It seems unintuitive.
- matm 14y agoVery keen observation. There are a number of ways to solve this problem. Machine learning helps (there are a few simple heuristics we currently use to sort the Event Feed). But the right interface for defining events helps even more. Sorry for the frustratingly mum response.
- pnt 14y agoWhat if you tracked the event's parents, e.g. button <- div <- .sidebar <- body, etc.? When presenting the events to the user, you could hide generic parents like 'div' and only show interesting parents with ids or classes. To search through events, perhaps the user could use css selector syntax in addition to the current UI you have.