Hi Eric, I think, there is a lot of "communication" between different parts of tw macros, with DOM attributes. Every button does it. I think, the whole page template, view template thing, works in a similar way. But I don't understand that process very well, yet.
I don't want to make a macro which writes to the DOM, and the next one, hides it, reads it, makes further processing, and does a different output. I thought there is a better way. I think some sort of "pipe" would be cool, but in a "noob" friendly way :) What I am looking after is: eg: A myOutput knows how to present lists for the user. A mySort knows, how to sorts lists A myFilter knows how to filters lists The user sais: Have a look to all tiddlers in the file, sort them alphabetically, and make a numbered output. -> mySort, myOutput it involved. Or. process all tiddlers, filter them by tag "xxx", filter the result by field "yyy", sort it descending by title and output it with tiddlylinks -> all three are involved, and filter two times. May be, everything is allready there and I don't see it. regards Mario On 20 Feb., 01:29, Eric Shulman <elsdes...@gmail.com> wrote: > > Has anyone thought about macro chaining at user lvl, which is > > supported by the core? > > > eg. a <<list>> passes its result to <<filter>> to <<sort>> and back to > > <<list>>, which displays it. > > When a macro produces output, it does so by generating and rendering > elements into the current 'place' in the DOM. As a consequence, there > really isn't a 'result' to be passed from one macro to another. > > -e -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to tiddlywiki...@googlegroups.com. To unsubscribe from this group, send email to tiddlywikidev+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
