Hey @TonyM So, I'm a little confused. It sounds like you you might be proposing two possibilities:
1. Have a filter which can be used to exclude tiddlers from being touched by Relink. Currently all non-shadow tiddlers are touched. But a filter would be feasible. 2. Propose having different relink configuration profiles for different categories of tiddlers. This sounds very complicated, not so much to design, but to present to the end-user. I'm also a little confused by your mention of the text field, I assume you mean a tiddler's text field, which refers to the body. Your example of text content was a note '"Old name" was renamed to "new name"'. But plain text like that wouldn't be touched anyway. Relink only targets reference-related instances of a renamed title. As to the dangers of renaming a dangerous system tiddler, I think I'd need to see an example. Since Relink doesn't touch shadow tiddlers, I'm not sure what harm could be done. The only tiddlers referencing shadow tiddlers are other shadow tiddlers, I believe. And I don't know of any system tiddlers that would break anything down if they were touched. Avoiding tiddlers like $:/backup or $:/trashbin might be examples. I guess they have some plugin or module that's creating and maintaining that. The solution to that ties into the first proposal I think you're putting forward: reasonable, though I would do something a bit more intricate than just a filter the user edits, so that plugins could introduce their own tiddlers to be exempt from relinking. Am I understanding you correctly? -Flibbles On Sunday, September 15, 2019 at 11:58:48 PM UTC-4, TonyM wrote: > > Fibbles, > > I was impressed with the potential of relink and received a request by a > client who uses a large Tiddlywiki database to allow them to change > someones name to their married name. The persons name a tiddler title > itself, is recorded in a range of fields and relink seems to detect them > all. However I have names mentioned in text fields such as a note saying > "Old name" was renamed to "new name" which I would like to exclude. Of > course I assume I can change the configuration to stop this. However > changing office names is also needed and these reside in another set of > fields. I assume just whitelisting all the list fields for all the tiddlers > I may wish to rename would work fine. > > However I am just wondering, I could in this case delete all the rules > that impact widgets, macro and filters because none of these should contain > something the user has any reason to rename. In some ways making it less > "pervasive" is possibly a wise design strategy, or is it?, what if they > rename a critical system tiddler? Would I prefer this to be relinked or > would it be best to prohibit relinking on system tiddlers? > > I am not sure there is a way for us to selectively filter to what relink > applies to? > > One idea may be to place a filter such that the relink action (when > renaming) does not appear, or take place on tiddlers that do not match the > filter. This would allow me to set a filter like > [all[current]object-type[office]] [all[current]object-type-person]] > which would use relink on the resulting tiddlers and any other tiddler not > in this filter would not permit relinking. Then as a designer I could > change this filter so relink will work for me when I am undertaking > designer activity and become active on say system tiddlers macros etc... > > I am yet to work through the extensive details of your wonderful plugin > and determine how it can best be used in a range of scenarios. It seems to > me this is not only a great tool to use to support end users, but to assist > in the development process. > > if I do not understand enough yet let me know, It would or could it be > desirable to have different relink configurations for different cases for > example for office and person do not relink items found in the text field, > but for tiddlers tagged $:/tags/Macro update all occurrences except in > tiddlers with the prefix $:/backup or $:/trashbin > > This is only food for thought, so please do not feel any pressure for a > refactor or re-write. I would be interested in your view. > > Thanks In advance > Tony > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/06ab81d2-92a5-405d-845c-a6621df706b8%40googlegroups.com.
