Yeah I think this should be done on the app level and not touch the blacklist in the engine. I am for keeping both seperate :) But maybe having a "hidden" option in the engines blacklist is a good option
2010/1/20 Mikkel Kamstrup Erlandsen <[email protected]> > So - I am pretty sure that we want said events in the actual DB, because > they are valuable behavioral info. I can definitely see the idea in not > showing them in the GUI. > > Perhaps we could drag some parts of the Blacklist extension from the > engine into a public lib, to easily serialize and deserialize a > collection of events. Then using Event.matches_template() (like the > blacklits ext. also does) would make it easy peasy implement this > feature in apps. > > -- > Option to never show specific items > https://bugs.launchpad.net/bugs/364102 > You received this bug notification because you are subscribed to The > Zeitgeist Project. > > Status in GNOME Activity Journal: New > > Bug description: > Some things are never interesting to have in the journal, because it's > always open, set as browser start page, etc. So, I'd like a context menu > option to "Never show this item". > Then maintain a blacklist of things that are always excluded from view. > > > > -- Option to never show specific items https://bugs.launchpad.net/bugs/364102 You received this bug notification because you are a member of GNOME Zeitgeist Team, which is the registrant for GNOME Activity Journal. Status in GNOME Activity Journal: New Bug description: Some things are never interesting to have in the journal, because it's always open, set as browser start page, etc. So, I'd like a context menu option to "Never show this item". Then maintain a blacklist of things that are always excluded from view. _______________________________________________ Mailing list: https://launchpad.net/~gnome-zeitgeist Post to : [email protected] Unsubscribe : https://launchpad.net/~gnome-zeitgeist More help : https://help.launchpad.net/ListHelp
