Saq,
As you are aware the wikification process is linked to the render process.
I am trying to keep this issue focused and fix the gap I have highlighted.
The term I try and use is "evaluate", basically to resolve a value from the
wikitext elements and use it in logic and other tests, ideally without
wikification, but evaluation. Can these be separated?, if not then
wikification would be a good target for preperformance improvements, it's a
nexus between the parsing and rendering, logic and practical use.
*Just as {{||template}} is not supported as a widget attribute,
{{{filter||template}}} is not supported for filtered attributes. *
I am not so sure about this statement. I understood the template
pre-processes the result then delivers the value(s) to the attribute. I
will look more closely.
Tones
On Friday, 4 December 2020 at 09:29:56 UTC+11 saq.i...@gmail.com wrote:
> @Tones wiki syntax for transclusions, and syntax for indirect and filtered
> attributes for widgets, are two entirely different things and changing them
> would not be backwards compatible.
>
> Refer to this thread that explains the same difference but with regards to
> double brace transclusions and indirect attributes:
> https://groups.google.com/g/tiddlywiki/c/YCdcBV88h_g
>
> Just as {{||template}} is not supported as a widget attribute,
> {{{filter||template}}} is not supported for filtered attributes.
> The filter is evaluated and the literal result of the filter is assigned
> to the attribute. Filters do not have any concept of templates.
>
> Regarding wikify, due to the performance implications, it is my personal
> opinion that we should NOT be facilitating its' usage and associated code
> patterns, and instead should be leading users towards more optimal ways of
> doing things. Wikify should be a tool of last resort when there are no
> alternative ways of doing the same thing. If you look through the TW core
> you will see that wikify is used exceedingly sparingly even though the
> entire UI is built from wikitext. Ultimately, however, it is not my call as
> what is supported in the core or not so its not me that you need to
> convince. :)
>
> That said, I do completely agree that we do need some better form of
> variable substitution or string templating support.
> Cheers,
>
> Saq
> On Thursday, December 3, 2020 at 11:17:24 PM UTC+1 TonyM wrote:
>
>> Saq,
>>
>> In effect are you a saying in the latter the reference to the value is
>> the result rather than the value?, I understand the complexities here (I
>> think) however I expect 99% of users
>>
>> - Do not understand this distinction
>> - Think the value is returned, and expects it in filter logic
>>
>> This is why I believe strongly we should provide a short method to do
>> this and my issue <https://github.com/Jermolene/TiddlyWiki5/issues/5110>
>>
>> Regards
>> Tones
>> On Thursday, 3 December 2020 at 20:32:33 UTC+11 saq.i...@gmail.com wrote:
>>
>>> An important distinction to make is that between filtered transclusions
>>> in wikitext, and filtered attributes for widgets.
>>>
>>> In the former, the {{{ filter || template }}} format is supported
>>> because the output gets wikified.
>>> In the latter, this is not supported as the literal value of the filter
>>> is assigned to the attribute, similar to attribute={{!!field}}
>>>
>>
--
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tiddlywikidev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/3a4d9328-65b2-4a47-a991-4af0e480a445n%40googlegroups.com.
