Yes, if I could modify the core items at start up via a plugin in such a way that it would not affect saving them out, then this would probably be ideal I think. Sort of a temporary removal of the tags that make them appear in the various places in the UI, etc...
I don't see any obvious place to do that either, or a way to do it that would not cause the changes to become permanent on the next save. It leads me back to, maybe it would be better for a plugin to attach new tags or flags and then have a global way to hook into filtering to specifically filter those out. That way if these tags/flags get persisted, it's not a big deal since the plugin won't actively hide them when loaded in a web browser. Short of directly replacing filters.js though I don't see a place to hook into that process. I think it is either that or I go an hunt down all the places in the Control Panel that have lists, tabs, etc.. and change the filter clause directly. That would just leave me having to fork those Core elements though, which I'd like to avoid. David On Monday, October 6, 2014 4:14:15 AM UTC-7, BJ wrote: > > 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 > -- 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.
