OK @Saq: I've taken a little run at creating a wiki to hold UseCase documentation for "TiddlyStreams" ; it's online at tiddlystreams.github.io , and if that looks to you like a move in the right direction, then i'll keep on going with it as time permits. If you or anyone wants to assist, i can add as users to the "tiddlystreams" organization, or i guess anyone can send a PR (it's a public repo)... or else just click the Comment Link (i.e. mailto:) at bottom of each tiddler.
Funny thing: your feedback has caused me to question my understanding of the term UseCase, so i did a bit of digging; sounds to me like what you want (if this article <https://www.visual-paradigm.com/guide/agile-software-development/user-story-vs-use-case/> can be considered definitive) is more like a UserStory set, while i- the naive (i.e. non-dev) user in this conversation- have been trying to communicate more in terms of a technical solution. Awkward! (like when i'm insisting on speaking Portuguese to a local who really wants to speak English with me :-) /walt On Sunday, July 11, 2021 at 12:13:14 PM UTC+1 saq.i...@gmail.com wrote: > @walt > > As to the node-flattening issue.... i would like to see "wikitext" join >> the other 3 options (bullet list, numbered list and paragraphs) >> > > So when I wrote "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" my expectation was for users to provide wikis > with a representative example of their content in streams nodes, as well as > a single tiddler version of it that they created by hand. For example one > tiddler with some stream nodes, the content of which is representative of > what their content is usually like. Plus one tiddler that is an > amalgamation of those nodes into a single tiddler. > > Having a few such examples might allow generalizing a few export options > that fit most use cases. The problem with receiving proposals for > solutions, rather than detailed description of the problem and related > content, is that often the proposed solutions don't fulfil the actual needs > or consider technical limitations they would impose. For example, your > proposed solution would limit you to only ever having single line content > in all your nodes. > > Regarding use cases/workflows, I was referring to the manner in which > people are using Streams for note taking (the original subject of this > thread). We have a few examples now from Keelan, Si and others. It would be > good to gather the descriptions of their workflows and add it to the > documentation. This could later be fleshed out with details on other > plugins, or wiki settings etc that they use to achieve their desired > workflow. Since there is not a single prescribed workflow for using > Streams, nor a vertical TiddlyWiki edition designed to accommodate it, > having examples of how people use Streams would allow knowledge sharing > amongst Streams user and be useful to the next person who has the same > question as you regarding how to use Streams for note taking. > > Help with collecting this to add it to the documentation would be greatly > appreciated. The easiest thing to do would be to collect the information in > a TiddlyWiki file. > > The other issue you've raised of particular interest to me is the mobile >> UseCase <#m_8733339352981130668_m_3548407170148151557_UseCase> - which >> may be more properly considered a UserModel >> <#m_8733339352981130668_m_3548407170148151557_UserModel> that could >> serve as extension to various UseCases >> <#m_8733339352981130668_m_3548407170148151557_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? >> > > Mobile usage is a tricky issue for TiddlyWiki. The design and UX really > isn't optimized for it. In particular, the drag and drop mechanism doesn't > work for all mobile browsers. This is a limitation of the browsers not > implementing the relevant spec at all or properly. As such, implementing > proper support for this is outside the scope of a single plugin. > > As I've expressed during earlier conversations on the same topic, I do not > intend to work on any mobile specific features or affordances for Streams > beyond any low hanging fruit that can be achieved with minimal effort. > Currently in Streams you can swipe on a node on mobile to trigger the > context menu. Add your own commands to the context menu is the way to go > for any features you absolutely need on mobile. > > The interest in the swipe with visual feedback feature actually comes from > a technical perspective. It is *very* impressive that such a thing can be > achieved with just wikitext, so I would like to see it realized (time > permitting) to serve as an example for others wanting to explore similar UX. > > 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/9f3958b4-e4a9-46a3-b5ff-3d859225e4f6n%40googlegroups.com.
