Encouraging news, @Saq -especially your process of continuous updates (with active notification in core would be GREAT!) and end-user engagement; best practices to emulate, IMHO.
As to the node-flattening issue: OK, so if we forget about that 2nd step of conversion to .md (or other) format for now, and focus on "consolidating your individual nodes into a single tiddler as wikitext" -this makes sense. As to next step: from my perspective, using @Jan 's streams-to-text addon, i would like to see "wikitext" join the other 3 options (bullet list, numbered list and paragraphs) in that pulldown menu of "Structure:" options at top RH corner of modal window... And this for me should preserve hierarchial indentation scheme, instead of just adding a * or a # to a flat list, as the first two options in existing pulldown do. Could this be a good next step to develop from your perspective, @Saq , @Jan? The other issue you've raised of particular interest to me is the mobile UseCase <#UseCase> - which may be more properly considered a UserModel <#UserModel> that could serve as extension to various UseCases <#UseCases>. This in my case involves using Quine2 on iOS devices: iPhone and iPad -2 different form factors, which lend themselves to somewhat different modes of interaction. What's needed here is the ability to manipulate position in the hierarchy via swipe L/R, drag Up/Down. Is this what you're talking about in that Reddit thread you shared <https://www.reddit.com/r/TiddlyWiki5/comments/o4wfcq/streams_visual_feedback_for_swipe_experiment/>? Or is there some other mode of mobile interaction to consider? As to documenting useCases: I'd be happy to pitch in on this, Saq, if you could advise as to which of the above two UseCases is most likely to be of constructive value in the near term. Q: Where to send such input? Is it to create "UseCase <#UseCase>: MobileNoteTaking <#MobileNoteTaking>" as an issue in your Github repo? Or do you prefer to engage such discussion here, or in Reddit, or...? /walt On Saturday, July 10, 2021 at 4:56:15 PM UTC+1 saq.i...@gmail.com wrote: > Hi everyone. I've been away on an impromptu leave the last week, apologies > for the late reply. > > I am very grateful to everyone that provided feedback or even just taken > the time to acknowledge that they use Streams. Thank you Keelan, Zhang, > Stan, Steph and everyone else. > > *@keelan* It is very good to hear that you are still finding Streams to > be of value. I thought of you a few weeks ago actually as yours was a > workflow and use case that really stood out to me, and I wasn't sure if you > had stuck with or turned to other tools. It is interesting how this works > in terms of feedback and involvement. From a user's perspective, if you > find a good tool you just want to use it and be productive rather than > focus overmuch on talking about the tool. However, for a very small > software project like this, occasional user feedback or even just holding > your hand up to acknowledge that you are still using it goes a very long > way. So thank you for taking the time to chime in here. > > *On flattening and export:* > In terms of export formats, the issue is that everyone's content and use > case is different which makes it difficult to come up with universal > solutions. One of the approaches here that could be interesting is if > everyone gave an actual real world example of what their content in Streams > is like, and what an ideal exported version in a single tiddler in > TiddlyWiki would look like. It might mean crafting that single consolidated > tiddler by hand to serve as an example. This might help generalize and come > up with a flexible solution. > > Note also that for some users, such as @si, it is a valid use case to not > want to consolidate all your nodes but keep them as separate tiddlers. > > I think the focus on markdown in this discussion is misplaced as it isn't > the primary barrier to exports from Streams. It really is two steps. a) > consolidating your individual nodes into a single tiddler as wikitext, and > b) then converting it to another format (HTML, markdown, etc.) Figuring out > the first step is necessary before looking at what comes after. > > *Use cases:* > We now have descriptions of a few different workflows with Streams. One of > the things that would be very helpful if we gathered this information and > added it to the documentation. This could be the first step towards > facilitating sharing of tweaks and settings etc that are being used in > those workflows. Any assistance with this would be very welcome. > > *Questionnaire, plugin updates and what comes next:* > I will likely post a questionnaire in the next week or two. A rather > preliminary one to get an idea of how many people use Streams and recruit > volunteers for testing new ideas and features. > > My policy moving forwards is going to be to make small incremental plugin > updates whenever I get the chance. Rather than spamming the group with > announcements, I will provide a simple opt-in plugin updates mechanism > until we have something in the core that serves the same purpose. See > https://groups.google.com/g/tiddlywiki/c/5eewU5jOUlc > > Group announcements of new updates will only be made if there is a > breaking change, or a critical bug discovered. > > I am tracking ideas for further development at github: > https://github.com/saqimtiaz/streams/issues > *Constructive and relevant* input is always welcome. > > Apart from the plugin update notifications, there are two other features > that I have prototyped and would like to find time to flesh out: > i) visual feedback for swiping on nodes (mobile): > https://www.reddit.com/r/TiddlyWiki5/comments/o4wfcq/streams_visual_feedback_for_swipe_experiment/ > > ii) a mechanism to easily see Streams keyboard shortcuts. In the video, > the overlay is triggered by holding ctrl+space for 2s, and automatically > closes when you let go of the keys: > https://drive.google.com/file/d/1y-hLpDZAhVLKEr9QA_4_jMV2oqla-Kys/view?usp=sharing > > 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/1ec59742-a017-40ef-a557-2a2b2e736f0en%40googlegroups.com.
