Si, Comments inline
> >>> but I would expect it is a little problematic because you are making > use of the short form of the transclude statement > > I'm assuming that by "short form" you mean using curly braces rather than > the transclude widget? If so how could I use the transclude widget to > generate multiple templates? > Yes, rather than curly braces you can use the tiddler widget to set a current tiddler and the transclude widget to name the tiddler. This allows you to add additional logic if an when needed. > > >>> My initial thought is to use a macro instead, even if that macro then > invokes a "transclusion view template" and then the transcludes the named > template. > >>> > >>> <<ingredient tomatoes>> > > Yes if this is possible then great, but how could I actually do it? I > would want to be able to generate a new macro for every tiddler with the > tag "type". As far as I can tell you can't define macros within a list > widget. > I will give this some thought, but no need for a new macro each time, just a macro that responds to parameters it is given. Personally I prefer to manage different tiddler types with a fieldname containing only one value eg; object-type=task rather than tags. > > >>> <<object ingredient tomatoes>> which could detect if "ingredients" is > defined, then if "tomatoes" is defined and provide create buttons, but once > created seek the ingredients and ingredient details and display as you > macro deems. > > Thanks I did not think of this (having a single macro which takes both > "type" and "linked tiddler" as parameters). It's not ideal but it's an > option I could use as a last resort. I'm not sure what you mean by "create > buttons" though. > Well, lets say I use <<object ingredient *new-food*>> a button would appear to create *new-food* similarly <<object *task taskname*>> a button to create the task object and taskname instance would appear. However if both exist just display or transclude. > >>> An approach is to use a macro with a list widget where ingredients is > the name of the template the list widget uses. > > OK now I'm lost. Can you give an example of what you mean? > \define show-ingredient(ingredient) <$list filter="[[$ingredient$]] template=ingredient> This is ignored because the tiddler "ingredient" is used to format the display of ingredient(s) and the current tiddler would be tomato </$list> \end <<show-ingredient tomato>> > > >>> Finally remember tiddlers (or fields for that matter) that are > transcluded can also transclude multiple levels deep. > > Yes but I can't see what the relevance of this is. Could you add a bit > more detail? > Only that you could transclude in a transclusion in a transclusion ... if that helped your design. eg you can transclude a field which contains a transclusion. For example see the caption field in core buttons such as $:/core/ui/Buttons/edit Given your questions I may do a some experiment's. Tones -- 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/fb88eca5-4b57-47c2-acd4-78d8c65f5120n%40googlegroups.com.
