Folks, Exploring the pre-release I can see the reduce operator is an advance, however these are my personal observations so far.
I understand the reduce operator has its origin in bigdata and other terminology, but it seems to me the documentation and examples is insufficient to realise its full potential for all audiences. - I may not be too smart, but neither am I a dummy, but the documentation is seriously hard to read. - Some of these features such as the index and accumulator would be nice in a regular filter, if they were available in the result of a list widget for example The reduce operator runs a subfilter for each input title, passing the result of the previous subfilter run as a variable. The initial value of the accumulator can optionally be specified. It returns the result of the final subfilter run. *The reduce operator runs a subfilter for each input title, * input-run > [reduce<subfilter>] ? *passing the result of the previous subfilter run as a variable * *(<accumulator>)* We should use quotes here "*previous subfilter run" as it needs this * In my words! *The subFilter is applied to each title in the input, each iteration off the subFilter can access the variable (<accumulator>) ie; "access the result of the previous iteration" . ie <accumulator> stores the result of the last subFilter. Thus if you use the add operator add<accumulator> to the subFilter you can sum all values.* *The following variables are available within the subfilter: <index> <accumulator> <revIndex> and <length> ONLY and <currentTiddler> varies with each title.* * The variables <index>, <revIndex> and <length> are available if you need these values to be part of your subfilter calculations.* *There is only ever one output from the reduce operator! * *The last value determined is the output of the reduce operator, as a result all subfilters would be expected to include an operation with the <accumulator> variable (eg add, multiply, divide etc..)* Regards Tones On Monday, 30 November 2020 at 22:36:42 UTC+11 [email protected] wrote: > I’m hoping that we’ll be able to release v5.1.23 of TiddlyWiki towards the > end of this week. There’s some discussion over on GitHub about the last few > loose ends to be tied up: > > https://github.com/Jermolene/TiddlyWiki5/issues/5130 > > The most important call to action is for developers of plugins and > adaptations to take this opportunity to verify that the new release doesn’t > break anything. > > The second call to action is for as many people as possible to put the new > release through it’s paces by performing a test upgrade of the wikis that > are important to them. Don’t switch over to the new version yet, of course. > > You can upgrade single file wikis here: > > https://tiddlywiki.com/prerelease/upgrade.html > > This is a really quite a massive release, with over 160 new features > listed in the release note. (I am working on improvements to the > presentation of the release note, it’s a bit of a wall of text right now). > > https://tiddlywiki.com/prerelease/ > > Just to mention a handful of new features that I’m particularly excited > about: > > * Keyboard support for the main core dropdowns: search, new tag, tiddler > type, new field, and the “link” button in the editor toolbar > * The beginnings of support for switchable page templates (referred to as > layouts), which will give us a route to introduce a more modern alternative > layout > * The ability to rename tiddlers during the import process (and to easily > see which incoming tiddlers will overwrite existing tiddlers) > * Many new filter operators that together make the TiddlyWiki filter > language significantly more powerful and expressive > * Improvements to the “tm-scroll” message making it possible to scroll to > positions within a tiddler > * Via the JSZip plugin, the ability to dynamically create ZIP files, > giving us the ability to create static sites in the browser > * New <$action-log> and <$log> widgets to aid debugging > > There are many, many bug fixes and other improvements too. > > As ever, I’m profoundly grateful to all the contributors who have pulled > together to make this such an exciting release. You can see here how much > activity there’s been since v5.1.22: > > > https://github.com/Jermolene/TiddlyWiki5/graphs/contributors?from=2020-04-16&to=2020-11-30&type=c > > My own contribution graph (below) shows nicely how this release covers my > illness and recovery from COVID, and undoubtedly a strange and painful time > for all of us. I couldn’t be more pleased that this community has thrived, > and seems to be working together so well at the moment. > > Please respond with any questions and thoughts here. > > Best wishes > > Jeremy. > > > > -- 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/2855b9f7-b2d8-4863-af1f-7c388951a298n%40googlegroups.com.
