Hi David, it sounds to me that you need to selectively override the cores' shadow tiddlers (remove their tags), that way changes would not be saved. Unfortunately I cannot see a straight forward way to do this (I think you can do it non-selectively by including the shadow tiddlers in your own plugin). I think it would be useful to be able to selectively install a plugin. (in a non-hacky way)
cheers BJ On Monday, October 6, 2014 9:51:29 AM UTC+2, David Jade wrote: > > Here's my thought - this probably doesn't exist but maybe it could in a > more generalized way if it was useful to others: > > Since most of the things I want to suppress or hide are part of the UI > because they are selected via tags, maybe I could somehow hook the filter > process to customize it with plugin code. If I could, then maybe I could > also extend the tiddler object to have a new custom field called > "isSuppressed" or "isHidden" - maybe via a tiddlermethod plugin. > > Then at the lowest level of the filter code, my custom hook would > basically never return those tiddlers - i.e. a filter global clause that is > always in effect (or at least in effect when my plugin is activated). I > think this would cause all the tiddlers to be effectively hidden in the > UI since they would never be selected in the various lists, etc... but it > wouldn't remove them from the saved state, etc... > > Maybe a way to do this is just to have a way to specify a global filter > clause that is always in, someplace inside filterTiddlers or compileFilter. > Or maybe via some sort of callback into plugin code that extends the > filtering process with custom code. > > This way I don't have to go and customize existing bits of Core or change > existing filter clauses in Core Tiddlers, etc... I could dynamically set a > property on the Tiddlers to flag that I want to suppress at run time and > then hook the filtering process to make them invisible for all instances > when they might be selected via any filtering. > > I'm pretty sure I could hack this in but perhaps being able to extend the > filtering process via plugin code in a generalized way would be useful to > others? > > Thoughts? > -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. For more options, visit https://groups.google.com/d/optout.
