@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 [email protected] 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 [email protected] 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 <[email protected]> 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 >>> [email protected]. >>> >> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1d3f7d7e-77fc-44d6-b8cf-1b0792db74c3n%40googlegroups.com.
