Thanks for replying Saq
It was a suggestion that if you find the peformance slowdown unacceptable,
> then you could replace the title matching filter in the detection code with
> one that just rejects fragments with disallowed characters. It would be
> faster though far less accurate.
>
OK. I assume the slowdown will increase with increased number of tiddlers
so yes, it's worth testing. Do you you think it would work well (and does
it make sense) to reject fragments that have any of all the triggers and
trigger ends? A $set to save them in a listvariable which is matched
against.
There are other options that could be explored via refactoring to try and
> get around the performance issues, but it would be a fair bit of work that
> may or may not yield results.
>
I'll try the "reject fragments etc" before asking about this.
Are you saying filtered transclusion {{{...}}} is evaluated for each stroke
>> but $list is not? [...]
>>
>
> No. [...] However, I did say that this is only an issue if its the display
> code causing the performance issues. So based on what you are reporting, I
> am unsure why you are focusing on this at the moment.
>
You're right. Thanks.
If you agree it makes sense to have the detection code match against a list
with the triggers and triggerends, that's what I'll try next.
Thank you Saq.
<:-)
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/tiddlywikidev/b2b7e1c9-0005-4cce-95e6-a5b9c8f97957o%40googlegroups.com.
