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



On Monday, September 2, 2019 at 12:27:19 PM UTC+10, Flibbles wrote:
>
> I present Relink <https://flibbles.github.io/tw5-relink/>!
>
> It relinks fields, links, WikiLinks, widgets, transclusions, lists, and 
> filters. It's highly customizable, but it will also work out of the box. 
> It's robust, and can handle bizarre name changes. It works through 
> whitelisting, so it doesn't change plaintext instances of a title, or other 
> instances where an updated would be undesirable. It's also well tested (but 
> still really new!!). It should be comprehensive.
>
> Otherwise, I really hope everyone gets good use out of this. Having 
> written it, I completely understand why this isn't a core feature. It was 
> *hard 
> as crap*! There are so many edge cases! I'm sure more will still crop up.
>
> *Edit**: It now also supports macros, making it a fully comprehensive 
> relinking plugin.*
>
> Demo page here <https://flibbles.github.io/tw5-relink/>.
>
> Source code here <https://github.com/flibbles/tw5-relink>.
>
> I would absolutely love to get some feedback. I really hope this helps 
> people.
>
> -Flibbles
>

-- 
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/c48a8669-3115-40ae-bd5c-8e3012accef2%40googlegroups.com.

Reply via email to