I thin that having macros treated differently when they are in the 'root' context (compiled to a macrocall widget) compared to when used as a parameter (textual substitution) is counter intuitive.
There is a need imo for a 'get' macro - <<get tiddler=x field=y>> and the macro parser need to be extended to enable nesting like <<get tiddler=<<get tiddler=y field=z>> >>. On Thursday, January 15, 2015 at 6:38:13 PM UTC-6, Tobias Beer wrote: > > Hi BJ, > > >> I do find using filters this way very contrived >> > a few 'helper' javascript macros to access tiddler fields >> > would make things (for my head at least) a lot easier. >> > > I totally agree. I'm quite glad, though, your head works the way it does. > Mine might have been sweating over this for another day or so. ^^ > > I also think that a lot of what I am doing > would be tremendously easier if I (most always) went with a js macro > rather than with this magick-voodoo-wikitext-kungfu. > > Best wishes, Tobias. > -- 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 http://groups.google.com/group/tiddlywiki. For more options, visit https://groups.google.com/d/optout.
