@Tony we seem to be talking about very different things. What is relevant and under discussion here is customizing the EditTemplate UI to offer a user interface for additional options related to renaming. The answer probably lies in adding a new edit template segment via a new tiddler which is displayed after $:/core/ui/EditTemplate/title
Streams has code for executing actions on tiddler rename (unpublished) and on tiddler delete (see https://github.com/saqimtiaz/streams/blob/master/plugins/streams/delete-hook/actions.tid) that may be of interest to you. If you wish to discuss that, please start a new thread. Thank you. Saq On Friday, September 4, 2020 at 2:25:59 AM UTC+2, TW Tones wrote: > > Saq, > > You know more than me I am sure, but here is what I know on this matter. > > Re-hackability in the rename, 1st it depends on the draft mechanism. Last > time I looked at it Relink uses a hack of its own, when it would be better > if tiddlywiki provisioned the hack for such tools. Eg a tag that will > include and have access to the rename process the current and new tiddler > at a minimum. Thus on rename a conditional process can be activated and > apply the rename according to its own rules. Ideally this would be a > generic solution. eg on rename trigger a mechanism that any solution can > add to. eg $:/tags/on-rename-actions. > > The next issue is renaming by other means. Ie copy and delete or > WidgetMessage: > tm-rename-tiddler > <https://tiddlywiki.com/#WidgetMessage%3A%20tm-rename-tiddler> > > Jeremy has a plan to expose the the actions behind WidgetMessages to > increase hackability which should allow the designer to install a custom > response to renames. However I am not sure how often tm-rename-tiddler is > used. > > I have a project I need to push forward that allows custom actions to be > included behind all existing buttons, this allows any button to be used as > a trigger. In this case the done/save button on a tiddler can trigger an > action to test for and handle the tiddler rename case. However to handle > this comprehensively one needs to deal with other buttons that trigger the > save process including those in other plugins. > > Regards > Tones > > On Thursday, 3 September 2020 21:21:26 UTC+10, Saq Imtiaz wrote: >> >> @keelan your description is in accordance with what I tried to express in >> my last message. The UI part might vary, as I haven't looked into how much >> flexibility there is to extend that part of the edit template, seeing as >> how Relink already customizes it. I'll investigate once I get the time and >> see what our options are. >> >> >> On Thursday, September 3, 2020 at 1:05:09 PM UTC+2 keela...@gmail.com >> wrote: >> >>> @Saq I'm not quite sure I'm following, though I imagine you're correct. >>> Let me rephrase to make sure I'm tracking with you. >>> >>> Are you suggesting that, like the relink plugin which triggers an option >>> to rename every mention of this tiddler once someone attempts to rename it, >>> Streams could (and should) suggest renaming the subnodes with that same >>> trigger? In this case, if I choose to rename a stream of nodes, I would get >>> a check box for the relink plugin *and *some form of checkbox asking if >>> I wanted to change the naming scheme of all stream nodes that are >>> "downstream" from this one. >>> >>> If that's what you're suggesting, I agree with your point. That does >>> seem to make more sense than adding something in the context menu. It seems >>> to create a more obvious user flow for renaming. That's the way I rename >>> things currently. I click on the bullet that I want to rename, enter edit >>> mode on the displayed tiddler, and then rename, making sure I have the >>> relink checkbox marked. It would make sense to also add a simple checkbox >>> here that would offer to rename all downstream tiddlers as well. This way, >>> a branch can become its own stream but stay a part of the initial stream as >>> well. It would make it searchable separately via the new method you've >>> established. And, if you started at the very beginning of a stream, it >>> would still rename everything downstream, changing the naming scheme on an >>> entire thread. >>> >>> If I'm understanding you correctly, this is a better approach. >>> >>> On Wednesday, September 2, 2020 at 5:01:42 PM UTC-5 saq.i...@gmail.com >>> wrote: >>> >>>> @Keelan regarding the rename handling we discussed, it occurs to me >>>> that it may make more sense to trigger this via the renaming of a tiddler >>>> the regular way via the edit template, rather than via renaming of a node >>>> via streams. >>>> >>>> Otherwise, there would be no mechanism to handle renaming the subnodes >>>> when the stream-root tiddler is renamed. Whereas a node can always be >>>> opened as a tiddler and renamed that way. >>>> >>>> What do you think? >>>> >>>> On Tuesday, August 25, 2020 at 2:44:07 PM UTC+2 keela...@gmail.com >>>> wrote: >>>> >>>>> That first option to rename if it shares the same prefix. >>>>> >>>>> I can see creating a steam in a particular topic, realizing it would >>>>> need a different title, and wanting to maintain the semantic connection >>>>> with all of the subnodes for the purpose of search. However, I would not >>>>> want to force a rename on one that I had already broken out with it's own >>>>> name. >>>>> >>>>> On Mon, Aug 24, 2020, 4:41 PM Saq Imtiaz <saq.i...@gmail.com> wrote: >>>>> >>>>>> @Keelan >>>>>> >>>>>> Is that something I could add to the context menu? I know you've set >>>>>>> it up so users can create their own menu items. >>>>>> >>>>>> >>>>>> Yes, that should be doable. >>>>>> There is some info here: >>>>>> https://saqimtiaz.github.io/sq-tw/streams.html#Extending%20the%20Context%20Menu >>>>>> >>>>>> I can probably help you get the actions right. Are you thinking an >>>>>> option that renames a node, and the subnodes *if* their titles begin >>>>>> with >>>>>> the node title? >>>>>> >>>>>> Or something to use after you've already renamed a node and the >>>>>> subnodes no longer match in terms of titles. >>>>>> >>>>>> -- >>>>>> >>>>> You received this message because you are subscribed to a topic in the >>>>>> Google Groups "TiddlyWiki" group. >>>>>> To unsubscribe from this topic, visit >>>>>> https://groups.google.com/d/topic/tiddlywiki/1jTwdmq8cgI/unsubscribe. >>>>>> To unsubscribe from this group and all its topics, send an email to >>>>>> tiddlywiki+...@googlegroups.com. >>>>>> >>>>> To view this discussion on the web visit >>>>>> https://groups.google.com/d/msgid/tiddlywiki/641a43dd-fb43-499f-8468-19c294358dd8n%40googlegroups.com >>>>>> >>>>>> <https://groups.google.com/d/msgid/tiddlywiki/641a43dd-fb43-499f-8468-19c294358dd8n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>> . >>>>>> >>>>> -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/126cf1b5-a05c-4af0-9103-efeea69c4a95o%40googlegroups.com.
