Mat,

As is often the case I think it depends on how you implement it. In one 
solution I built I had a dozen object different object-type tiddlers, and 
each of these had there own view and edit templates. However the view 
template only took the current tiddlers object-template field, obtained the 
object name and added a prefix eg $:/objects/viewTemplates/objectname and 
transcluded that.

Therefor the bulk of which was used to display the view template was only 
transcluded on demand.

I saw no performance issues.

Regards
Tones

On Wednesday, 19 May 2021 at 23:15:25 UTC+10 Mat wrote:

> I've heard cautions against using many viewtemplates, for performance 
> reasons.
>
> But what, *specifically*, causes the poorer performance from this?
>
> For example, it doesn't make sense that it would be to locate the 
> templates because it is still only one search trough *all *tiddlers 
> regardless if the filter finds one template or a hundred (...right?)
>
> So is it rather what the viewtemplate shows that can be a problem? E.g if 
> a viewtemplate has a lot of nested lists? ...but in that case, one such 
> viewtemplate could be worse than 10 simpler viewtemplates so it would not 
> warrant caution from using many viewtemplates *per se*.
>
> Or is the problem if there are *many open* tiddlers? Beacuse each of them 
> shows all viewtemplates? So it is "N open tiddlers" times "M number of 
> templates". But then the templates only deserves half the blame.
>
> Does the caution change when one uses "conditional viewtemplates", i.e 
> viewtemplates with a wrapping listwidget like
>   <list filter="[all[current]tag[foo]]">...</$list> 
> ?
>
> In summary: What is the actual problem with many viewtemplates?
>
> Thanks!
>
> <:-)
>

-- 
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 view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/84af76de-eb5a-4422-979d-2e5fba0af8ean%40googlegroups.com.

Reply via email to