Hi Mat The system tags like $:/tags/ViewTemplate are implemented by a fragment of wikitext like this:
<$list filter="[all[shadows+tiddlers]tag[$:/tags/ViewTemplate]!has[draft.of]]" variable="listItem"><$transclude tiddler=<<listItem>>/></$list> It sounds like your OP is a proposal to make that construction pervasive by effectively turning every transclusion within the core templates into an instance of that construction. On the face of it, the problem is that each of those transclusions would have to get a little more complicated in order to include information about the system tag that is to be used to extend it. Another issue is that pulling in tiddlers by tag is significantly less efficient than transcluding a single tiddler. Therefore we don’t want to pay the price for that work unless we need it. That means that we need to explicitly mark up the transclusions that should be extensible in this manner, which brings us straight back to the present way of things. Best wishes Jeremy. > On 28 May 2018, at 01:25, TonyM <anthony.mus...@gmail.com> wrote: > > Mat, > > I understood, you were not targeting any tiddler, but a global solution that > supports the visual components as well as other use cases, is what I am > ading. The fact is this mechanism to use a set of tags to determine what > appears is not only increasing pervasive in the core but a smart thing to do > when developing our own solutions and plugins. I would add the ability to > pass a filter into it and it would have a great utility. I have also done > something similar with fields in the current tiddler in mymenus plugin. > Personaly I am always looking to universalise changes since it is in keeping > with TiddlyWikis whole architecture, just as your proposal so anything can be > placed anywhere. > > Regards > Tony > > On Thursday, May 24, 2018 at 5:35:58 PM UTC+10, Mat wrote: > CLARIFICATION of OP > > I expressed something poorly. > > But wouldn't it make sense to generalize this so that anything can be placed > anywhere? It should not be necessary to have an explicit ListWidget in only > certain "container tiddlers"; instead any tiddler could be a potential > "list-start" that other tiddlers can be prepended or appended onto. We are > currently pretty limited in this regard. > > I didn't mean "any tiddler", I meant; any visual component. And by "visual > component" I mean visually identifiable "objects" such as tiddlers, fields, > widgets (more?) where it can be relevant to inject something. > > <:-) > > > > -- > 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 > <mailto:tiddlywikidev+unsubscr...@googlegroups.com>. > To post to this group, send email to tiddlywikidev@googlegroups.com > <mailto:tiddlywikidev@googlegroups.com>. > Visit this group at https://groups.google.com/group/tiddlywikidev > <https://groups.google.com/group/tiddlywikidev>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywikidev/a9e0817b-c5ff-419f-8544-11fd7f47207d%40googlegroups.com > > <https://groups.google.com/d/msgid/tiddlywikidev/a9e0817b-c5ff-419f-8544-11fd7f47207d%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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 post to this group, send email to tiddlywikidev@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/8B4AAA29-9730-4F84-8F0F-36ADF967EF71%40gmail.com. For more options, visit https://groups.google.com/d/optout.
