Zhang. Please share that solution if possible, it looks great.
Tones On Friday, 2 July 2021 at 10:22:38 UTC+10 [email protected] wrote: > @Saq > > One of the things I would dearly like to know is how many people are > actually using Streams on a regular basis, and what their workflow looks > like. My feeling is its a very small handful and I'll admit that probably > influences how much time I devote to working on Streams. > > I've been using streams regularly for a bit over a month, initially as a > replacement for RoamResearch. After awhile I have to say TiddlyWiki > combined with Streams is so much more flexible and "sensible" than vanilla > RoamResearch. For example, I was able to implement RoamResearch-style > backlinks with Streams' macros: > [image: backlink.PNG] > So Just joined the group to say thanks to you for your marvellous work! > > On Thursday, 24 June 2021 at 15:59:33 UTC+1 [email protected] wrote: > >> Hi Walt, >> >> Hopefully you will get input from people actually using Streams as to >> what works for them. >> >> One of the things I would dearly like to know is how many people are >> actually using Streams on a regular basis, and what their workflow looks >> like. My feeling is its a very small handful and I'll admit that probably >> influences how much time I devote to working on Streams. >> >> >>> But then: the result is a slew of tiddlers with long numeric IDs that, >>> tho nicely presented in the edit window as a clean hierarchal outline, >>> cannot be either flattened into a single tiddler, nor exported or even >>> copy/pasted into the tiddler body via any built-in affordance. I've been >>> going the copy/paste way so far, but it's a hard road to travel, given any >>> significant length and/or complexity to your outline. >>> >> >> Have you considered any of the methods outlined here? >> https://saqimtiaz.github.io/streams/#Working%20with%20streams%20tiddlers >> >> Now: plugin author Saq said essentially >>> <https://groups.google.com/g/tiddlywiki/c/vlAZ_K4K63o/m/9lO63cZEAQAJ> >>> that the only reason he hasn't built in any such affordance is that he >>> >> doesn't know what users want: a simple concatenation of the stream? a >>> hierarchial structure in some form? >>> >> >> It's a bit more than that. Each node in a stream is a tiddler and can >> have any content. Streams was originally envisioned not just for rapid note >> taking but also for the ability to divide your text into smaller tiddlers >> as you write/edit. As such it is difficult to envisage a single export >> format that would work for everyone's content. However using the >> approaches outlined in the link above you can easily set up your own >> markdown export. >> >> >> >>> For me, the best (and simplest?) solution would be to convert the stream >>> to Markdown: each node being just a line of text preceded by a number of >>> asterisks (1->any) to reflect its level in the hierarchy. >>> >> >> The issue is that MD tiddlers will always be second class citizens in >> TiddlyWiki. I think in the long run this isn't going to be a feasible >> approach unless all you want to do is write your notes and export them >> outside of TiddlyWiki. Also note that while MD syntax does support >> multiline content in lists, TW markup does not ( at least not cleanly). >> >> As an aside, I think something like this unfulfilled experiment would >> suit your use case from what I know of it: >> https://groups.google.com/g/tiddlywiki/c/drA7IEx2Ng0/m/67pyPkgKBgAJ >> Before you ask, no plans to take that any further, in part due to the >> reasons outlined above. >> >> Cheers, >> Saq >> >> -- 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/571b57b3-532f-4a28-a7a3-0b7cccbcf360n%40googlegroups.com.
