Mat,
I am not suggesting we document every permutation of replaceable parameters but
that most examples include at least one especially when the appropriate ones
are limited. I also think a full macrocall version for macros also makes sense
because it can contain all the key=value pairs for parameters so we can copy
it, paste it and alter the parameters as needed. The macrocall version works
well with most replaceable parameters.
When there are different forms of a widget they could be spelt out in an
example.
The gap we need to address is examples with only literals do not demonstrate
the best approach to coding.
When a designer creates a macro to capture the parameters to supply one or more
widgets they open the design to allow the passing of parameters of most
variables etc...
Personally I am happy to raise the Push requests or documentation changes
because it saves me time in the end.
Using the double curly braces raised in this thread only the $(var)$ and $var$
are workable and they only operate in macros. Also using {{||template}} is easy
because it assumes currentTiddler so a good design pattern is to write most
macros to operate on current Tiddler. If we can give users these hints in the
doco I think we reduce the barriers to adoption.
Personally I find most of the examples illustrative but I never use them
because they contain named tiddlers and are unusable in any way except specific
cases, Not in global macros or the view template.
regards
Tony
--
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 post to this group, send email to tiddlywiki@googlegroups.com.
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/f7ae0f76-f732-45d7-ba07-2091b3a5d5f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
