Jed or better yet
<$macrocall name=list-links param=<<SomeFilter>> /> After identifying the name of param. *To all* In relation to the overall thread, the emphasis I believe should be placed on the fact wikiText is "evaluated" before Widgets are actioned, or we would not be able to feed widgets with changing variables as in the above example <<SomeFilter>> must be "evaluated first" to allow its result to be passed to the widget. Thus when we say <<list-links <<SomeFilter>> >> What is to be evaluated first? <<list-links <<SomeFilter>> (notice we open and close "<< >>") <<list-links >> then <<SomeFilter>> illogical <<SomeFilter>> then <<list-links resulthere>> that is what we mean is it? So this example <<list-links <<SomeFilter>> >> fails to be clearly defined because something needs to be evaluated before the whole is evaluated. Arguably Tiddlywiki could be designed to tear this statement apart, and deal with the nesting implicit in this, however why do all that when you can turn it into a widget call and have the parameters evaluated before calling the widget? On Monday, 18 February 2019 21:43:29 UTC+11, Jed Carty wrote: > > I think that this is something that would be best explained with examples. > You could have the statement there as well and then have some examples to > show it and link to a tiddler with a more in-depth explanation for people > who want it. > > Something like: > > This works: > > <$list filter=<<SomeFilter>>> > > </$list> > > this doesn't: > > <<list-links <<SomeFilter>>>> > > > and put in some more examples and maybe a quick explanation of why, like > the one that doesn't work is trying to use a macro calling a macro. I think > that it would be ok to have only one or two examples on the main part and > then link to more examples for people who want them. > > In this sort of thing I think a good general design principle is to start > with the shortest and simplest, or most direct, explanation possible and > then let the person reading it decide if they want more by giving links to > more in-depth explanations and examples. > Unfortunately saying that is easy, making something that is that way is > the hard part. > > We could add something like 'as a general guideline, if it starts with > this <$ it can have this << inside it and not this <$, but if it starts > with this << it can't have this <$ or this << inside it.' > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/005e8625-dedf-4b4c-a931-aca9d62f2a91%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
