I was thinking in terms of the existing syntax. So at the moment <<tiddler MyTemplate>> would render the tiddler MyTemplate. The only different is that MyTemplate is currently rendered in the context of the tiddler MyTemplate (itself).
So possibly context might be a better name then data? My motivation here is I could imagine a macro (in fact I am working on one) which allows you to pass a filtered list of tiddlers through a template eg.<<tiddlers MyTemplate filter:[tag[systemConfig]]>> I think this would be really useful for mimicking most types of loop from a tiddlyweb templating perspective, but would also be a powerful alternative to the forEachTiddler plugin... Jon On 17 Nov, 13:55, Paul Downey <[email protected]> wrote: > > <<tiddler MyTemplate data:foo>> > > > This would render the tiddler MyTemplate in the context of the tiddler > > foo. > > I like the idea, but dislike the formulation and the use of the name > "data". Suggest something more explicit, such as: > > <<tiddler template:MyTemplate tiddler:foo>> > > but that's without thinking of the implications or if this is a > generic parameter change, or only applies to the tiddler macro. > > -- > Paul (psd)http://blog.whatfettle.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en -~----------~----~----~----~------~----~------~--~---
