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. 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/a9e0817b-c5ff-419f-8544-11fd7f47207d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
