I noticed another ongoing thread where the user in question was expecting
to be able to render wikitext into an attribute: Read here
<https://groups.google.com/d/topic/tiddlywiki/XH4tgLlr7fY/discussion>.
He is trying to generate a filter expression using <$list> widgets,
presumably to cull duplicated items in a recursive search. His calling
code is thus:
<$set name="myList" value=<<listDescendants "NameOfConceptTiddler">> >
<$list filter=<<myList>> />
</$set>
(where <<myList>> is a recursive macro involving <$list>.)
I suspect this isn't an entirely uncommon sticking point.
On Saturday, 12 September 2015 11:52:24 UTC-5, Evan Balster wrote:
>
> Use Case:
>
> Suppose within my TiddlyWiki I'm rendering an infographic as SVG. The SVG
> contains a path, which is defined by a string containing a list of
> vertices. Suppose further I want to use an operation with at least one
> <$list> widget to populate this path, as below. Because the path is an
> attribute string, any transclusion into it will not be wikified. I can
> paste transclusions together using macros, but that isn't practical for
> lists. So is there a way to *force* wikification?
>
> Obviously any HTML would be undesirable in the output, so I would need to
> be able to use a render mode like the one which applies in this typed block:
>
> $$$*text/vnd.tiddlywiki>text/plain*
> <$list filter="[tag[Vertex]first[]]">M {{!!x}} {{!!y}}
> </$list>
> <$list filter="[tag[Vertex]rest[]]">L {{!!x}} {{!!y}}
> </$list>
> $$$
>
> (I ran into this problem a few months ago while creating a graphical
> timeline generator and never managed to solve it. I know this is possible,
> because TiddlyWiki does something very similar to support customized
> stylesheets with basic parsing rules -- but I've investigated how it's
> done, and the mechanism uses calls to the rendering engine in core code
> rather than any accessible macro. The discussion I started at that time
> did not lead anywhere.)
>
> As far as I can tell, all that would be necessary would be a macro to the
> effect of:
>
> <<*parse_and_render* {{MySVGCode}} text/vnd.tiddlywiki>text/plain>>
>
> Which makes the appropriate calls into core code. Would this be
> reasonable to request as a core feature? If not, is there a plug-in?
>
>
> (I anticipate someone will mention that this is possible by way of storing
> data to a temporary tiddler and then transcluding it. If so, I *would*
> love to know how -- but I also point out that such is a significant
> deviation from TiddlyWiki's "normal" way of rendering things and makes
> unnecessary use of long-term storage. I'd also rather avoid "refresh"
> trigger buttons.)
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywiki/e63160c8-af22-4488-bc6c-e0b54131dcab%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
