Haha, I noticed a lot of fabulous comments in the code. Yes, a good teaching repository. I learned a lot from searching for definitions and implementations in the TiddlyWiki repo, but Streams has a bunch of things I wanted to do in it (of course). With discipline and time, I would ideally check every one of my macros against Streams to look for better code patterns.
On Tuesday, August 4, 2020 at 3:22:57 AM UTC-4, Saq Imtiaz wrote: > > @clutterstack Streams is actually written in a rather verbose manner to > make it easier to follow the code logic. The intention is for it to serve > as a reference implementation for this kind of functionality. This has > actually held me back from adding some features that would improve the > writing experience, as it would add complexity. So the goal was to get it a > version 1.0 and freeze that as the reference implementation and then add > more features for later versions. > > In my ideal scenario, someone builds on the examples provided by Streams > to create something that makes Streams obsolete. ;) > > Regarding re-writing and also just debugging complex and lengthy wikitext > actions, it can be a bit of a pain when to debug when things don't go as > planned. > In such situations you may find this useful: > > https://saqimtiaz.github.io/sq-tw/sandbox.html#%24%3A%2Fsq%2Fwidgets%2Faction-log > > You can use it to dump all variables as a table to the developer console > from actions. > <$action-log/> > or > <$action-log $message="the name of the step being debugged"/> > More examples in that tiddler itself. > > Cheers, > Saq > > On Tuesday, August 4, 2020 at 2:58:33 AM UTC+2, clutterstack wrote: >> >> @Saq, I'm glad you are not bothered by the similarities. I didn't think >> you would be, given your track record of sharing on here. I tried in the >> first instance to incorporate most of the features of my half-baked Vue app >> to leverage TiddlyWiki in-place (since everything I wrote was intended to >> feed tiddlers to my wikis in the end), and not to peek too much at Streams >> etc., because I was curious to know where I would end up. Now I have >> something that functions fairly well according to my original intentions, >> but of course I can see ways to make it better, and I've started looking to >> see where your decisions were similar or different. >> >> Thanks again for the encouragement! >> >> On Monday, August 3, 2020 at 5:17:31 PM UTC-4, Saq Imtiaz wrote: >>> >>> Despite the significant similarities, I am very pleased that you're >>> working on this and sharing your progress. The TW community needs more >>> active developers, and the best way to get started and learn is often by >>> means of a passion project. >>> >>> It is pretty normal to need a rewrite after creating the first proof of >>> concept. Do no let that discourage you. Even Streams is in need over a >>> thorough review and refactoring for efficiency and performance. >>> >>> Do feel free to ask if you have any questions or difficulties moving >>> forwards. >>> Cheers, >>> >>> Saq >>> >>> >>> >>> On Monday, August 3, 2020 at 10:21:39 PM UTC+2, clutterstack wrote: >>>> >>>> Hello all, >>>> >>>> Following on from my quick adder plugin, I've built a demo of the >>>> reason I wanted the quick-adding capability. >>>> >>>> I was pretty excited about this, and I guess I still am, although it >>>> converges quite a lot toward Streams and NotoWritey. It's called Omni, >>>> short for Omnibus, because each one collects tiddler "passengers". Here's >>>> what I said in the demo are its basic capabilities: >>>> >>>> * Quickly add tiddlers, without needing to think of a title right away >>>> (or ever) >>>> * Rearrange tiddlers within and between omnibuses by drag and drop >>>> * Drag and drop to add tiddlers to the omnibus >>>> * Add (existing) tags to tiddlers by drag and drop >>>> * Set indentation levels or styles for tiddlers within the omnibus >>>> * "Fold" and "unfold" tiddler transclusions >>>> >>>> I see I Ieft out "edit tiddler text". You can see there's some overlap, >>>> although there are some slightly different decisions among Streams, >>>> NotoWritey, and Omni. >>>> >>>> Demo and some notes are available at >>>> https://clutterstack.github.io/TW5-omni/ >>>> >>>> Having used this for a bit, I have come to the conclusion it needs a >>>> major reworking under the hood, but there's a lot I will keep. Certainly, >>>> the fact that I know Streams is much better-written is due to my having >>>> climbed a learning curve writing this -- I can now read and understand >>>> Saq's code. >>>> >>>> Anyway, although this is not a production-ready plugin, maybe someone >>>> will get an idea or snippet from this. The plugin repo is >>>> https://github.com/clutterstack/TW5-omni. >>>> >>>> I plan to incorporate more ways to manipulate and assemble "omnibuses" >>>> into my wiki. My historical problem has been that I can collect a lot into >>>> a wiki but it's a bit of a black hole after that. >>>> >>>> Cheers, Chris >>>> >>> -- 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/d9613c28-345c-48d0-a62f-622c710896bdo%40googlegroups.com.
